LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 11-04-2019, 03:45 PM   #31
khronosschoty
Member
 
Registered: Jul 2008
Distribution: Slackware
Posts: 462
Blog Entries: 2

Rep: Reputation: 286Reputation: 286Reputation: 286

Quote:
Originally Posted by montagdude View Post
If you aren't even able to take a stab at it, I'm afraid that creating a parser and slackbuild generator on top of it is going to be a failure from the outset. No one is going to spend time on this if they feel like it will be wasted, and certainly not if you are not even willing to post a best-effort first attempt.

My recommendation: create your own SlackBuild scripts for a bunch of different stuff. Then you will learn the ins and outs of the process and the potential pitfalls of what you are currently trying to accomplish. If, after having done that, you still feel this project is a good idea, go forward with it and ask for help with specific items.
I know you (the original poster) don't want to hear this; but this is actually very good advice (that montagdude shared with you). Some time ago, I don't know how many years ago, I thought I could improve SlackBuild's by making an easier to read explanation; however, I never managed in my mind to do a better job then what I've seen others do; or even a better job then just reading the SlackBuild templates themselves. If you were to give it a go, however, and showed me something that looks promising I would praise that effort; and offer help if it is within my ability to offer it.

Last edited by khronosschoty; 11-04-2019 at 03:51 PM.
 
1 members found this post helpful.
Old 11-04-2019, 04:06 PM   #32
igadoter
Senior Member
 
Registered: Sep 2006
Location: wroclaw, poland
Distribution: many, primary Slackware
Posts: 1,405

Original Poster
Blog Entries: 1

Rep: Reputation: Disabled
Quote:
Originally Posted by khronosschoty View Post
If you were to give it a go, however, and showed me something that looks promising I would praise that effort; and offer help if it is within my ability to offer it.
I will do nothing just for to be patted on my back. So it seems my idea doe not sounds promising. interesting, or maybe people here are rusted completely, not capable for slightest change of everyday routine - or I am not allowed into fifth circle of most blessed Slackware gnostics. Ok, but let put irony aside. Can we go back to subject? Just can you tell me what do you think slackbuild script is?
 
Old 11-04-2019, 04:14 PM   #33
khronosschoty
Member
 
Registered: Jul 2008
Distribution: Slackware
Posts: 462
Blog Entries: 2

Rep: Reputation: 286Reputation: 286Reputation: 286
Quote:
Originally Posted by igadoter View Post
I will do nothing just for to be patted on my back. So it seems my idea doe not sounds promising. interesting, or maybe people here are rusted completely, not capable for slightest change of everyday routine - or I am not allowed into fifth circle of most blessed Slackware gnostics. Ok, but let put irony aside. Can we go back to subject? Just can you tell me what do you think slackbuild script is?
A bash script used to package software, already compiled binaries, recently compiled binaries, re-package binaries, or virtual any other kind of computer data in a manner fit for use with Slackware's pkgtools suit.
 
1 members found this post helpful.
Old 11-04-2019, 04:24 PM   #34
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 7,734

Rep: Reputation: 6297Reputation: 6297Reputation: 6297Reputation: 6297Reputation: 6297Reputation: 6297Reputation: 6297Reputation: 6297Reputation: 6297Reputation: 6297Reputation: 6297
Quote:
Originally Posted by igadoter View Post
I will do nothing just for to be patted on my back. So it seems my idea doe not sounds promising. interesting, or maybe people here are rusted completely, not capable for slightest change of everyday routine - or I am not allowed into fifth circle of most blessed Slackware gnostics. Ok, but let put irony aside. Can we go back to subject? Just can you tell me what do you think slackbuild script is?
From the Slack Docs Wiki https://docs.slackware.com/slackware:slackbuild_scripts:

Code:
A SlackBuild script is a shell script (usually Bourne shell compatible) that automates the process of configuring,
compiling and creating a Slackware package (*.tgz, *.txz, *.tbz files) from source archives.
I really wonder why you keep wasting other people's valuable time with essentially a trivial nonsensical question which has been answered before.
 
3 members found this post helpful.
Old 11-04-2019, 04:46 PM   #35
0XBF
Member
 
Registered: Nov 2018
Location: Winnipeg
Distribution: Slackware
Posts: 92

Rep: Reputation: Disabled
Trying to write a universal slackbuild that tries to simplify the user experience to such a level will require enormous complexity in the scripting to cover all possible build configurations and options the user might ever need. IMO you will have better luck just building all third party packages and maintaining a repository for something APT style like ubuntu uses. Personally I would not want to take on either project.
 
Old 11-04-2019, 05:04 PM   #36
igadoter
Senior Member
 
Registered: Sep 2006
Location: wroclaw, poland
Distribution: many, primary Slackware
Posts: 1,405

Original Poster
Blog Entries: 1

Rep: Reputation: Disabled
Quote:
Originally Posted by Alien Bob View Post
From the Slack Docs Wiki https://docs.slackware.com/slackware:slackbuild_scripts:

Code:
A SlackBuild script is a shell script (usually Bourne shell compatible) that automates the process of configuring,
compiling and creating a Slackware package (*.tgz, *.txz, *.tbz files) from source archives.
I really wonder why you keep wasting other people's valuable time with essentially a trivial nonsensical question which has been answered before.
This sentence is very good starting point now let go forward for more details. One need to put inside information about architecture - but nope it is not really needed it can be resolved. But pair "architecture": value should be allowed for exception only 32 bit or 64 bit. The lat sentence is an example of thing I would hope to discuss. Some parts of script are completely fixed: #!/bin/sh -e. They are out of question. They are not a part of description. So description contains things which can change. Name of package, version etc. For local scripts licensing is irrelevant. I don't need license to run script I made for myself. Engine should allow to create script on base of description validated by script schema. All is done on local system and there is no attempt made to publish script. This is how to manage system. How to customize system in compatibility with other scripts. Shortly: every package outside default set is being added by creating appropriate script. Script by itself is not important it can be each recreated by script description. Now we just need to do some static and look for diversities between sbo scripts. How different they are. To answer question: they are really so different so it is not possible to create scheme for script description?
 
Old 11-04-2019, 05:24 PM   #37
montagdude
Senior Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 1,613

Rep: Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251
Sounds like you have a good idea of what you want to accomplish. Why don't you just go ahead and try it then? You don't need us to give you a bunch of information up front. Just start with a template, plug in some variables, and see if it can generate a working SlackBuild script for some software in a "blind test." If not, fix the problems and iterate. Come back here when you need help with specific problems. That is the way to approach this project if you are really serious about it, not by asking us to tell you all the possible inputs up front.

Last edited by montagdude; 11-04-2019 at 05:26 PM. Reason: Autocorrect
 
Old 11-04-2019, 05:24 PM   #38
igadoter
Senior Member
 
Registered: Sep 2006
Location: wroclaw, poland
Distribution: many, primary Slackware
Posts: 1,405

Original Poster
Blog Entries: 1

Rep: Reputation: Disabled
Quote:
Originally Posted by 0XBF View Post
Trying to write a universal slackbuild that tries to simplify the user experience to such a level will require enormous complexity in the scripting to cover all possible build configurations and options the user might ever need.
Your statement is essentially untrue. If it was then building any application would be enormous complex task. About build configurations: even package driven distribution do not guarantee application works as required. It is always generic build. But essentially possible build configuration is also a problem of already existed sbo scripts. To know how many build option is covered by script one need to run configure utility and compare with what is inside script. To validate quality published build script I would have to go through all process of configuration.
 
Old 11-04-2019, 05:31 PM   #39
drgibbon
Member
 
Registered: Nov 2014
Distribution: Slackware64 14.2
Posts: 513

Rep: Reputation: 332Reputation: 332Reputation: 332Reputation: 332
SlackBuilds are a very simple manner of building packages. Like I said before, they are mostly just straightforward collections of the very things you'd type at the command line to, in the end, produce a Slackware-compatible binary package (with some detection of certain things built in, sometimes specific to the particular software being built, amongst other possibilities).

I'm sorry, but there is just no way your project is going to fly if you have to ask people "what a Slackbuild is". You really need to understand them to be able to produce them in a coherent manner through some automated means. Just start making some, possibly to submit to SBo, that would be great. Later on you can try and improve the whole process.

Btw, if you want to see something more streamlined for ideas, maybe take a look at Void's system.

Last edited by drgibbon; 11-04-2019 at 05:35 PM.
 
Old 11-04-2019, 05:33 PM   #40
kikinovak
MLED Founder
 
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: CentOS, OpenSUSE
Posts: 3,408

Rep: Reputation: 2019Reputation: 2019Reputation: 2019Reputation: 2019Reputation: 2019Reputation: 2019Reputation: 2019Reputation: 2019Reputation: 2019Reputation: 2019Reputation: 2019
Quote:
Originally Posted by igadoter View Post
Nope, it is not a solution I am looking for. Human-readable means that everyone even person with zero knowledge of bash would build its own packages - just provide correct description according to scheme - parse this to bash script with parser. At the end run the script.
Jason Cannon's Bash courses on Udemy are great for learning shell scripting.

If you don't want to learn, then you'd probably be better off with a different distribution.
 
Old 11-04-2019, 05:42 PM   #41
igadoter
Senior Member
 
Registered: Sep 2006
Location: wroclaw, poland
Distribution: many, primary Slackware
Posts: 1,405

Original Poster
Blog Entries: 1

Rep: Reputation: Disabled
Quote:
Originally Posted by kikinovak View Post
If you don't want to learn, then you'd probably be better off with a different distribution.
Do you think to be arrogant is a luxury? So what would you propose for someone who don't want to learn? Or maybe just create a poll: vote which distribution in your opinion is for people who don't want to learn? Debian, Ubuntu, Fedora, CentOS, Mint, PCLinux, OpenSuse - I am listening for other propositions.
 
Old 11-04-2019, 05:48 PM   #42
khronosschoty
Member
 
Registered: Jul 2008
Distribution: Slackware
Posts: 462
Blog Entries: 2

Rep: Reputation: 286Reputation: 286Reputation: 286
Quote:
Originally Posted by igadoter View Post
Do you think to be arrogant is a luxury? So what would you propose for someone who don't want to learn? Or maybe just create a poll: vote which distribution in your opinion is for people who don't want to learn? Debian, Ubuntu, Fedora, CentOS, Mint, PCLinux, OpenSuse - I am listening for other propositions.
Question? Are you assuming he doesn't prefer one of those distros?
 
Old 11-04-2019, 05:59 PM   #43
igadoter
Senior Member
 
Registered: Sep 2006
Location: wroclaw, poland
Distribution: many, primary Slackware
Posts: 1,405

Original Poster
Blog Entries: 1

Rep: Reputation: Disabled
Quote:
Originally Posted by khronosschoty View Post
Question? Are you assuming he doesn't prefer one of those distros?
Those I listed I don't think a quite suitable for don't-want-learners. So I asked for other propositions. Personally I never hear about such distribution. Seems it is empty space to fill - create distribution for don't-want-learners.
 
Old 11-04-2019, 06:00 PM   #44
Qury
Member
 
Registered: Feb 2004
Location: Dublin
Distribution: Slackware
Posts: 181

Rep: Reputation: 163Reputation: 163
so, what my understanding about this whole topic is that OP would like to see a simplified abstraction layer to generate ither build scripts or to actually build the package. Like a yaml or JSON file akin to Dockerfile???

If that is the case then it is an interesting idea, however i don't see the point
 
Old 11-04-2019, 06:38 PM   #45
igadoter
Senior Member
 
Registered: Sep 2006
Location: wroclaw, poland
Distribution: many, primary Slackware
Posts: 1,405

Original Poster
Blog Entries: 1

Rep: Reputation: Disabled
Quote:
Originally Posted by Qury View Post
so, what my understanding about this whole topic is that OP would like to see a simplified abstraction layer to generate ither build scripts or to actually build the package. Like a yaml or JSON file akin to Dockerfile???

If that is the case then it is an interesting idea, however i don't see the point
Exactly. Point is to reach compatibility along Slackware instances. Sbo builds are one of the sources of packages - but not the only one. For example. Someone needs to add an object to system. There is no build script - what to do? I think good solution is to create own build script following template for sbo builds. But again this would require knowledge of scripting say intermediate level. So it is no good. Instead of let provide simple textual description - no need for bash scripting is required. For simple builds it should be enough. Of course if someone is ambitious person and is trying to build huge bundle - then pure clean person is on his own. Similar situation is for software for very particular purposes. But I would never use myself sbo script for such software. In other words: only relatively simple task can be covered by scripts only for general use applications.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Suitesparse /Cuda SBo, complains about too advanced GCC, although being built with GCC 5 from the same SBo. Lockywolf Slackware 5 04-28-2019 11:17 PM
nvidia-driver SBo The symbolic link '/usr/lib/libGL.so.1' does not point to 'tmp/SBo/package-nvidia-driver/usr/lib64/libGL.so.1' Gerardo Zamudio Slackware 5 07-30-2017 11:44 PM
Questions for Robby, ponce, or anyone from SBo about SBo submission requirements. ReaperX7 Slackware 4 06-07-2015 12:30 PM
Nvidia-driver.SlackBuild from SBo (or: I am a bad and sloppy SBo maintainer) kingbeowulf Slackware 8 08-31-2012 03:41 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 08:06 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration