SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The SBo scripts are really only a starting point. I modify every single one to use the most recent version, run on -current, and install in ~/.local.
If anything could be improved, it is that SBo needs to rethink its strategy of targeting -stable. That worked well with yearly releases, but does not work well now.
Ed
I find the SBo works just fine as a starting point, even with -current.
The system works well for me. All my machines run stable.
Quote:
Originally Posted by chrisretusn
I find the SBo works just fine as a starting point, even with -current.
I will be more blunt: if SBo were a company, its management would be replaced. Waiting for 15.0 was a failed strategy. The new management would adopt a strategy of targeting -current.
Ed
I will be more blunt: if SBo were a company, its management would be replaced. Waiting for 15.0 was a failed strategy. The new management would adopt a strategy of targeting -current.
Ed
do you volunteer to patch, test and maintain SBo for -current throughout its development and evolution?
My "local" tree contains my testing tree for potential updates to my SlackBuilds.
But for actually compiling packages I use the stock SlackBuilds.org git tree (the sbopkg default).
Thank you and thanks all for the discussion. I can understand the "model" behind SlackBuilds now and seems a good trade-off. We can use it as a starting point and branch/maintain it by ourselves.
In that sense, any doc/tutorial about linking/adding a local git repo into sbopkg? I found:
Code:
$ cat /etc/sbopkg/repos.d/60-SBo-current.repo
# DO NOT EDIT THIS FILE. CHANGES WILL BE OVERWRITTEN. See the README.
# Repo Branch Description Tag Tool Link CheckGPG
SBo-git current "UNSUPPORTED SBo git repository for -current" ponce git git://github.com/Ponce/slackbuilds.git@current ""
Can I add a new file in that repos.d folder?
How can I point to a local directory? Like how to set the `Tool` and `Link` fields?
I think that targeting -current would not be more work than targeting 1-2 stable releases per year.
Ed
You failed so spectacularly with this offensive reply that you earned a place on my ignore list. Or prove me wrong and remove your hands from under your ass and start contributing - for free.
Can I add a new file in that repos.d folder?
How can I point to a local directory? Like how to set the `Tool` and `Link` fields?
If I recall correctly, the sbopkg.conf file is already wired up to support the local repository; you just have to populate it (my local repository only has my own SlackBuilds):
Code:
drumz@darkstar:/var/lib/sbopkg/local $ ls
network/ system/
The hierarchy is the same as /var/lib/sbopkg/SBo/14.2/
Then you tell sbopkg to use the "local" repository instead of the default (14.2) repository by "-V local".
Of course, you could edit the configuration files to change your default repository or add more repositories.
You failed so spectacularly with this offensive reply that you earned a place on my ignore list. Or prove me wrong and remove your hands from under your ass and start contributing - for free.
I didn't mean to offend volunteers.
I have handed to Pat quite a few bug reports and fixes over the years. I do this because I want a working OS.
Ed
What a wonderful Tool. I watch it herd kats everyday. so I stay away from it and Do like Pat. Pull what I need.
Slack builds is great. love and use it at times. copy the scripts. Tried to put a dev Team together in 2015 to do stuff but Slackbuilds SBO did a ububtu thing let new break the stable distro. Right now slackbuild is almost obsolete NOT their fault.
It is the Slacker way. No such thing as 14.3 so lets just build our own and use the tool.
I will be more blunt: if SBo were a company, its management would be replaced. Waiting for 15.0 was a failed strategy. The new management would adopt a strategy of targeting -current.
Ed
Since they never target stable. It is a field . The devs make stuff work and they dump it in the field say look it's new. But hey look Willy. We can make stuff work in Slack. Sure it will cause other to break stuff. But hey it is a dump. recycle and sort. So it has nothing to do with stable or current. It is a dump. and the dump has good stuff and trash.
And huge builds that break teams stuff. so. take a snapshot of the Dump and sort it. then build your own dump for your team the tools all the same.
And the SBO teams Tool is world class. top. The latest-est SBOPKG by far the best thing that ever happen to slackware.
I strongly advise against changing that because it will mean that when you and everybody else will send the pull requests to the maintainers or the SBo admins, for each one of them they will have to:
- test the new build;
- test the update against whatever needs it as a dependency;
- contact the respective maintainers and track their answers;
- if the maintainer is unresponsive try to find a new mantainer.
it's much more practical when these steps are done by whoever is interested in the update (and is ready to step in as a maintainer himself) and has tested it locally.
Put in your stuff on git opens this. You can filter by actual team invites. May want to learn the admin thing.
Ton of work till you filter it to the accepted team members ok you have 500 team members and they have there there own repo. So you see. your making work . By doing everyone else work. lets take SSR for example slackers deal with His git for years. I am one. now it is in Slackware. But when I had issues with the builds I took it to The maintainers git HG SVN etc.
I tried to handle it through SBOPKG but hey. not going to work. So fix it before it gets in the door.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.