LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
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 09-11-2020, 03:28 AM   #16
chrisretusn
Senior Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 1,290

Rep: Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550

Quote:
Originally Posted by EdGr View Post
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.
 
Old 09-11-2020, 09:55 AM   #17
EdGr
Member
 
Registered: Dec 2010
Location: California, USA
Distribution: I run my own OS
Posts: 483

Rep: Reputation: 234Reputation: 234Reputation: 234
Quote:
Originally Posted by drumz View Post
The system works well for me. All my machines run stable.
Quote:
Originally Posted by chrisretusn View Post
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
 
1 members found this post helpful.
Old 09-11-2020, 10:45 AM   #18
solarfields
Senior Member
 
Registered: Feb 2006
Location: slackalaxy
Distribution: Slackware
Posts: 1,103

Rep: Reputation: 668Reputation: 668Reputation: 668Reputation: 668Reputation: 668Reputation: 668
Quote:
Originally Posted by EdGr View Post
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?
 
1 members found this post helpful.
Old 09-11-2020, 10:55 AM   #19
EdGr
Member
 
Registered: Dec 2010
Location: California, USA
Distribution: I run my own OS
Posts: 483

Rep: Reputation: 234Reputation: 234Reputation: 234
Quote:
Originally Posted by solarfields View Post
do you volunteer to patch, test and maintain SBo for -current throughout its development and evolution?
No, I am too expensive.

I think that targeting -current would not be more work than targeting 1-2 stable releases per year.
Ed
 
Old 09-11-2020, 11:31 AM   #20
solarfields
Senior Member
 
Registered: Feb 2006
Location: slackalaxy
Distribution: Slackware
Posts: 1,103

Rep: Reputation: 668Reputation: 668Reputation: 668Reputation: 668Reputation: 668Reputation: 668
Quote:
Originally Posted by EdGr View Post
No, I am too expensive.
this shouldn't be an issue, since SBo contributors and maintainers do it for free
 
Old 09-11-2020, 11:49 AM   #21
jmpz
Member
 
Registered: Jul 2012
Posts: 58

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by drumz View Post
Yes:

Code:
sbopkg -V local -k -b ffmpeg.sqf
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?
 
Old 09-11-2020, 11:51 AM   #22
hitest
Guru
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, Debian
Posts: 6,351

Rep: Reputation: 2588Reputation: 2588Reputation: 2588Reputation: 2588Reputation: 2588Reputation: 2588Reputation: 2588Reputation: 2588Reputation: 2588Reputation: 2588Reputation: 2588
Cool

Quote:
Originally Posted by Daedra View Post
The current system works, no need to fix something that isn't broken.
Agreed. I'm very grateful for the work done by the good people at SBo.
 
1 members found this post helpful.
Old 09-11-2020, 12:30 PM   #23
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,129

Rep: Reputation: 6991Reputation: 6991Reputation: 6991Reputation: 6991Reputation: 6991Reputation: 6991Reputation: 6991Reputation: 6991Reputation: 6991Reputation: 6991Reputation: 6991
Quote:
Originally Posted by EdGr View Post
No, I am too expensive.

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.
 
5 members found this post helpful.
Old 09-11-2020, 02:31 PM   #24
drumz
Member
 
Registered: Apr 2005
Location: Scottsdale, AZ, USA
Distribution: Slackware
Posts: 256

Rep: Reputation: 105Reputation: 105
Quote:
Originally Posted by jmpz View Post
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.
 
1 members found this post helpful.
Old 09-11-2020, 03:31 PM   #25
EdGr
Member
 
Registered: Dec 2010
Location: California, USA
Distribution: I run my own OS
Posts: 483

Rep: Reputation: 234Reputation: 234Reputation: 234
Quote:
Originally Posted by Alien Bob View Post
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
 
Old 09-11-2020, 04:26 PM   #26
lovemeslk
LQ Newbie
 
Registered: Feb 2020
Location: none of your business
Distribution: Slackware
Posts: 17

Rep: Reputation: Disabled
My thoughts on SBO

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.

Last edited by lovemeslk; 09-11-2020 at 04:31 PM.
 
Old 09-11-2020, 04:50 PM   #27
lovemeslk
LQ Newbie
 
Registered: Feb 2020
Location: none of your business
Distribution: Slackware
Posts: 17

Rep: Reputation: Disabled
Quote:
Originally Posted by EdGr View Post
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.
 
Old 09-11-2020, 05:08 PM   #28
lovemeslk
LQ Newbie
 
Registered: Feb 2020
Location: none of your business
Distribution: Slackware
Posts: 17

Rep: Reputation: Disabled
Quote:
Originally Posted by ponce View Post
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.
 
Old 09-11-2020, 06:06 PM   #29
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1.2 on Lenovo Thinkpad W520
Posts: 9,479

Rep: Reputation: Disabled
Others don't do that either. For instance the AUR (Arch User Repository) is not managed using git, but users can comment like e.g. here.
 
Old 09-11-2020, 10:39 PM   #30
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 4,204

Rep: Reputation: 1431Reputation: 1431Reputation: 1431Reputation: 1431Reputation: 1431Reputation: 1431Reputation: 1431Reputation: 1431Reputation: 1431Reputation: 1431
Quote:
Originally Posted by lovemeslk View Post
I tried to handle it through SBOPKG but hey. not going to work. So fix it before it gets in the door.

it is handled in the development version of sbopkg. It's not going to be backported to the version we have in stable now unfortunately.
 
  


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
openbox on slack13.37 (x86) -- Thanks to linuxquestions.org, slackbuilds.org & many vectrum Linux - Member Desktop Screenshots 5 02-03-2013 12:22 PM
slim pkg from slackbuilds.org symatic Slackware 3 07-14-2007 02:53 PM
[slackbuilds.org] slackware repository idea arcanex Slackware 5 05-19-2007 09:19 PM
Use SlackBuilds.org or my own hosting to offer up SlackBuilds? hollywoodb Slackware 6 11-30-2006 08:56 PM
SlackBuilds.org Frozen Bubble not working... Lufbery Slackware 7 11-07-2006 01:54 PM

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

All times are GMT -5. The time now is 07:07 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
Open Source Consulting | Domain Registration