LinuxQuestions.org
Help answer threads with 0 replies.
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 05-17-2020, 12:34 AM   #1
dchmelik
Member
 
Registered: Nov 2008
Location: Washington state, USA
Distribution: FreeBSD Unix, Slackware, FreeSlack GNU/Linux, OpenBSD Unix, FreeDOS
Posts: 460

Rep: Reputation: 51
pkgtools/slackpkg(+,) slapt-get, sbopkg/sqg, autoslackpkg, hoorex, mkslack, sbotools, sboui, slackroll, slackyd, slpkg, spkg, spman: which?


Pkgtools were probably on the old official Slackware CD I tried in the 1990s, and I used and programmed for Slackware more & more since (though had a short desktop break until recent drivers, still used Slackware for servers)... a bit newer than pkgtools are official slackpkg and unofficial slapt-get, sbopkg/sqg, autoslackpkg, hoorex, mkslack, sbo-templates, sbotools, sboui, slackpkg+, slackyd, slackroll, slpkg, spkg, spman, even more than that... what's good for what?

Slackware does have dependency management: Patrick Volkerding makes sure each release has all dependencies if you do a full installation, and any new upgrades (mostly for security) will have dependencies at that time. You don't manage its dependencies on your own (except for example, if you install in a server you may not have much space, don't need X, but if it runs a site, you might need some X libraries, so you learn that advanced knowledge on your own.)

Apart from official package tools, first I mostly used sbopkg since '00s, then switched to sbotools (though sbopkg has sqg, which makes it just as powerful, and I saw one or two errors in sbotools sbopkg didn't make)... then I started using slackpkg+ with more repositories, sometimes even SlackOnly.com... then I tried slpkg, which if I recall correctly (IIRC) did some new things I liked, but couldn't figure out some things about it (a few years ago, kept saying it needed an update which wasn't in its repository) nor could figure out how to use sboui for multiple repositories (but seems it would be very nice to use)... now there's also autoslackpkg, which if I could figure out how to blacklist & greylist right, might also be powerful.

There were some difficult things to learn about each tool, but they saved a lot of time, even in the case that they manage dependencies (just not ones that won't cause the official Slackware to not boot, as far as I know)... for any/all of these, what are some things some do that you think they might do better than others? If you use most/all, would you use different ones for different things? Are there any other Slackware package tools you are aware of (ignoring stuff like dpkg or rpm, which I typically would never use... but past tools to build/install BSD Unix packages were interesting.)

If you build packages and submit them to SlackBuilds.org (or another public repository) of course also comment in relation to that and/or any package build tools (or ones named slack*, or that do similar things) if might be interesting...

If I recall correctly, slapt-get might've been the earliest unofficial, and in the '00s I almost/fully ruined my system with it, but if one knows about it, it might be useful, and Salix package management tools might be useful in some case (even graphical in the case you might administer a PC for users but they might want to view & install packages.) I mean, if a server has a password anyway, why not use a tool that might make updating some things easier (is that the case with Salix?) Currently I don't on my servers for some reason (something else the Salix fork did) but maybe it was easier for somoene elses's server (even if I think I might still not try that.)

Maybe because of what everyone used to say about slapt-get (and why they don't use it unless they understand it well) it's strangely the case that on Usenet and some of the original Internet Relay Chat (IRC) some people still don't even want to use the official slackpkg. Slackpkg never caused a problem for me, but it was once the case something unexpected happened with slackpkg+ that I had to reinstall slackpkg (i.e., maybe even boot install .ISO to rescue, find & reinstall slackpkg with a special argument/flag/switch to mean in /mnt rather than /!)

Of course the sbo* tools, slpkg, etc., can also do such things: if you use current, they might overwrite system packages with older versions for stable, from before when those packages were brought in (unless you can select 'clear installed,' like in sbopkg; unsure about sbotools or others.)

So in summary, be extremely careful with any unofficial tool (or quasi-official ones, as one repository is run by Slacksware team members, so I consider the repository/tool quasi-official, but most the packages unofficial) because unexpected/error things can happen... if you learn a tool and get used to it, that becomes less likely...

Personally I like slackpkg for official system updates & (carefully) slackpkg+ (for prebuilt repositories,) sbopkg if I want to read through the unofficial package lists (but sbopkg and the Slackware installer need to expand the boxes to more rows & columns for modern monitors, as a friend of mine explained is possible with GNU Dialog,) but mostly sbotools to install those (or sbopkg if it didn't work)... sometimes I might've used slpkg if I was trying repositories not in slackpkg+ yet, or just to learn different tools... still want to learn sboui and autoslackpkg (every night I already get update lists with cron and almost every day do updates sort of likeautoslackpkg does, so see no reason to keep typing it all out...)

Last edited by dchmelik; 05-23-2020 at 11:39 PM.
 
Old 05-17-2020, 05:00 AM   #2
bormant
Member
 
Registered: Jan 2008
Posts: 380

Rep: Reputation: 211Reputation: 211Reputation: 211
As for me, sbopkg has command line switches for most of usage cases, so no any need to see dialog windows ;-)
 
2 members found this post helpful.
Old 05-17-2020, 07:54 AM   #3
Chuck56
Member
 
Registered: Dec 2006
Location: Colorado, USA
Distribution: Slackware
Posts: 616

Rep: Reputation: 200Reputation: 200Reputation: 200
I can help with autoslackpkg. You mention slackpkg blacklist and slackpkg+ greylist as hurdles to work through. Start with the blacklist, post a copy and let's take a look.
 
1 members found this post helpful.
Old 05-17-2020, 12:17 PM   #4
hitest
Guru
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, OpenBSD
Posts: 6,200

Rep: Reputation: 2429Reputation: 2429Reputation: 2429Reputation: 2429Reputation: 2429Reputation: 2429Reputation: 2429Reputation: 2429Reputation: 2429Reputation: 2429Reputation: 2429
I like and use official Slackware tools on my Slackware64-current desktops and laptops(pkgtool, slackpkg). I also appreciate and use sbopkg to manage my third party applications. I rarely compile applications from source, but, I appreciate that Slackware allows me to do that.
 
1 members found this post helpful.
Old 05-19-2020, 12:02 AM   #5
dchmelik
Member
 
Registered: Nov 2008
Location: Washington state, USA
Distribution: FreeBSD Unix, Slackware, FreeSlack GNU/Linux, OpenBSD Unix, FreeDOS
Posts: 460

Original Poster
Rep: Reputation: 51
Quote:
Originally Posted by Chuck56 View Post
I can help with autoslackpkg. You mention slackpkg blacklist and slackpkg+ greylist as hurdles to work through. Start with the blacklist, post a copy and let's take a look.
Thanks for offer. It'll be some hours/days/weeks before I get back to that stage. What I recall happened in slackpkg+ is I blacklisted a few packages... they were still installed... maybe I even blacklisted an entire repository except for specific packages--if possible--but that didn't do much. It's been a few years since I used it (since temporarily switched on desktop for amdgpu drivers, but use Slackware on laptop and servers without many packages) but actually I may not really be using it much until next stable Slackware .ISO, because otherwise I can't use most repositories; I'm on Slackware-current.

I noticed on upgrade to Slackware-current, sbotools were broken... I think recompiling them fixed it... except what repository to specify. I switched to mostly using sbopkg but build the queues with sqg... sbotools handles queues, which would be quicker often (except browsing) because it's command-line...
 
Old 05-19-2020, 09:41 AM   #6
montagdude
Senior Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 1,743

Rep: Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334Reputation: 1334
This hasn't been widely tested, but you should be able to use sboui for multiple repositories by creating an additional configuration file, then calling it like this:

Code:
sboui -f /path/to/custom/sboui.conf
At a minimum, the new configuration file will need a different repo_dir and repo_tag. However, you will also need to configure the backend package manager to use the alternate repository. If you are using the built-in package manager, you can need an additional configuration file (sboui-backend.conf) for that purpose and point to it with the CONF environment variable in sboui. The most consistent way to do that would be to set it in your custom sboui config file, like this:

Code:
# Partial contents of /path/to/custom/sboui.conf
repo_dir = "/var/lib/sboui/alternate_repo"
package_manager = "built-in"
install_vars = "CONF=/path/to/custom/sboui-backend.conf"
upgrade_vars = "CONF=/path/to/custom/sboui-backend.conf"
And then, finally, in your custom sboui-backend.conf:
Code:
# Partial contents of /path/to/custom/sboui-backend.conf
REPO_DIR=/var/lib/sboui/alternate_repo
Like I said, this is not well tested, so if you try it, let me know what works or doesn't. One issue I can see right away just by looking at the code is that if you use the UI to change options, it is going to overwrite the main config file rather than the custom one, so don't do that. I will put it on my list of things to fix.

Last edited by montagdude; 05-19-2020 at 09:47 AM.
 
Old 05-19-2020, 09:43 AM   #7
chrisretusn
Senior Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 1,133

Rep: Reputation: 467Reputation: 467Reputation: 467Reputation: 467Reputation: 467
What's good for what? Well I can only speak to slackpkg with slackpkg+. I've always used slackpkg to keep my system updated. Before slackpkg+ I used pkgtools primarily for 3rd party packages using blacklist to make sure I didn't accidentally on purpose remove 3rd party program with 'slackpkg clean-system'.

Then slackpkg+ came out. That was a game changer. Once you have a handle on how slackpkg+ works with slackpkg it make upgraded a piece of cake. I no long need entries in blackist for third party packages. I created my own repository for my builds and mirror everything except for slackpkg+ and slackpkgbeta. There is no download time when I do an upgrade across my LAN. Each system has a few 3rd packages differences that are handled by slackpkgplus.conf. I also make use of graylist and notifymsg.conf.

I maintain one desktop and three laptops. I've never really tried any of those other programs as I am quite satisfied with slackpkg with slackpkg+.
 
1 members found this post helpful.
Old 05-20-2020, 05:40 AM   #8
dchmelik
Member
 
Registered: Nov 2008
Location: Washington state, USA
Distribution: FreeBSD Unix, Slackware, FreeSlack GNU/Linux, OpenBSD Unix, FreeDOS
Posts: 460

Original Poster
Rep: Reputation: 51
How chrisretusn does things also sounds amazing. I was just going back through sbopkg and found several other package tool, management, build, tracking, etc. programs... some had unusual names, like weren't slack*, sl*, s*... I'll have to go back through and add them to the list unless someone does. They weren't all in the same category maybe. I think one started with m.
 
Old 05-23-2020, 11:37 PM   #9
dchmelik
Member
 
Registered: Nov 2008
Location: Washington state, USA
Distribution: FreeBSD Unix, Slackware, FreeSlack GNU/Linux, OpenBSD Unix, FreeDOS
Posts: 460

Original Poster
Rep: Reputation: 51
Looking through SlackBuilds again, the number of package/build-script download, build, installation, creation, management, tracking, etc. tools is simply amazing. Others I'm wondering about now are porg (Slackware-specific or not,) conan (C/C++-specific, but Slackware-specific,) and there are probably 10+ others, not just dpkg & rpm (feel a little sick now, but one might only want to make a directory to view/decompress such, then if it might work without Debian/Redhat aspects, or what dependencies are) and also many tools for using/building other language (Perl, Python, ...?) packages on Slackware.<br><br>

I admit, though I also have Slackware laptop, servers, I'd been away from it on desktop for a couple years for display drivers (which kingbeowulf now built.)<br><br>

Even noticing the package install/build/maintain/track possibilities since then is really amazing but I have to get up to speed, and it looks like any new users might have some weeks/months just trying these approaching 20 different ones (I couldn't list some above, like findpkg, listpkg sound like pkgtools but unofficial...
 
  


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
autoslackpkg - a way to automate slackpkg Chuck56 Slackware 45 01-13-2020 07:42 AM
Curious: pkgtools Directories and SymlLnks with pkgtools-15.0-noarch-20.txz on Thu Jun 21 22:58:42 UTC 2018 kjhambrick Slackware 4 06-23-2018 01:16 AM
[SOLVED] dialog screen mangled when running slackpkg or pkgtools as root (but not sbopkg) Paulo2 Slackware 25 04-21-2018 02:04 PM
sbopkg/sqg vs sbotools? Didier Spaier Slackware 2 11-11-2015 04:39 AM

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

All times are GMT -5. The time now is 03:01 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