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.
Can you blacklist packages from certain repositories, like 'alienbob:bitcoin' which hasn't been updated in years so is many versions behind the official version?
No on the blacklist.
There are two ways to handle this.
This first (and simplest) is to create a directory (e.g., /home/non-slack/sbopkgs/) and put the bitcoin package in it. You could put all your SBo packages in this directory. Then add this to slackpkgplus.conf:
Add this new repository to REPOPLUS and to PKGS_PRIORITY. With PKGS_PRIORITY make sure sbopkgs is before any repositories i.e., alienbob. Make the entry as "sbopkgs:bitcoin"; e.g., PKGS_PRIORITY=( sbopkgs:bitcoin alienbob ). If your have more than one SBo package in this directory and you want them take precedence over repositories then use "sbopkgs:*" PKGS_PRIORITY=( sbopkgs:* alienbob ).
Be sure to run 'slackpkg update' after modifying slackpkgplus.conf.
The second (and best method in my opinion) is to use gen_repos_files.sh from https://slackware.nl/people/alien/tools/ to generate the files needed to create a local repository for your SBo packages. Make sure to read the script, configuration will be needed. A gpg key is highly recommended. I would recommend creating a .genrerc file. Place all of your SBo packages in a directory (e.g., /home/non-slack/sbopkgs/), run the script. If setup correctly you have your own repository. The add this to slackpkgplus.conf:
Add this new repository to REPOPLUS and to PKGS_PRIORITY. With PKGS_PRIORITY make sure it is before any repositories you want sbopkgs to take precedence over; e.g., PKGS_PRIORITY=( sbopkgs alienbob ).
Run gen_repos_files.sh like this or just set the USERDEFS variable in gen_repos_files.sh
This based of of one of my .genrerc files as an example:
Code:
# The directory of the Slackware package repository:
REPOSROOT="/home/non-slack/sbopkgs/"
# Repository maintainer
REPOSOWNER="Name <email@address>" << This will be used by gpg
# The GPG key for the repository owner can contain a different string than
# the value of $REPOSOWNER . If you leave $REPOSOWNERGPG empty, the script will
# use the value you've set for $REPOSOWNER instead to search the GPG keyfile.
REPOSOWNERGPG=""
# Under what URL is the repository accessible:
DL_URL="file:///home/non-slack/sbopkgs/"
# The title of the generated RSS feed:
RSS_TITLE="My SBo Slackware packages"
# The logo picture used for the RSS feed:
RSS_ICON="file:///home/non-slack/phearSW.png" << pick your own logo
# The URL linked to when clicking on the logo:
RSS_LINK="file:///home/non-slack/sbopkgs/"
# URL to the full changelog.txt:
RSS_CLURL="file:///home/non-slack/sbopkgs/ChangeLog.txt"
# The descriptive text for the RSS feed:
RSS_DESCRIPTION="My SBo Slackware package repository."
# Maximum number of RSS feed entries to display:
RSS_FEEDMAX=15
# The RSS generator must use a unique feed identifier.
# Generate one for your feed by using the string returned by "uuidgen -t":
RSS_UUID="" You need to do this
# Either use gpg or gpg2:
GPGBIN="/usr/bin/gpg"
# Optionally use gpg-agent to cache the gpg passphrase instead of letting the
# script keep it in the environment (note that if you define USE_GPGAGENT=1
# but gpg-agent is not running, you will get prompted for a passphrase every
# single time gpg runs):
USE_GPGAGENT=0
# Generate slack-requires, slack-suggests, and slack-conflicts lines in the
# metadata files by setting FOR_SLAPTGET to "1" -- these are used by slapt-get
FOR_SLAPTGET=0
# Follow symlinks in case the repository has symlinks like 14.0 -> 13.37
# indicating that one package works for those two Slackware releases.
# If the script does _not_ follow symlinks, then the symlinks will appear in
# the repository listing instead of the packages they point to.
FOLLOW_SYMLINKS=0 # default 1 << I have no symlink in my repository so set this to '0'
# If the repository has separate package subdirectories (for separate
# Slackware releases or architectures) then define them here.
# Separate FILELIST.TXT, MANIFEST etc.. files will be created for all of them:
REPO_SUBDIRS=""
# If you want to exclude certain directories or files from being included
# in the repository metadata, define them here (space-separated).
# Example: REPO_EXCLUDES="RCS logs .genreprc"
REPO_EXCLUDES=".genreprc" << This file
# ---------------------------------------------------------------------------
# By default, no debug messages 0
DEBUG=1
# Timestamp to be used all around the script:
UPDATEDATE="$(LC_ALL=C date -u)"
# A value of "yes" means that .meta .md5 and/or .asc files are
# always (re)generated.
# while "no" means: only generate these files if they are missing.
FORCEMD5="no" # .md5 files
FORCEPKG="no" # .meta files
FORCEASC="no" # .asc files
TOUCHUP="no" # rsync has issues with files whose content has changed, but
# both size and timestamp remain unchanged (needs expensive
# '--checksum' to detect these file changes)
# We may have a need to only update the ChangeLog files:
RSSONLY="no" # ChangeLog .rss and .txt
# For a sub-repository we do not have a ChangeLog:
CHANGELOG="yes"
# Variable used to limit the search for packages which lack .md5/.asc file,
# to those packages changed less than NOTOLDER days ago.
NOTOLDER=""
# Variable used to import the content of a text file as the new ChangeLog.txt
# entry. If empty, you will be asked to type a new entry yourself.
LOGINPUT="changelog.update.txt" << I use this file for entering to add entries to ChangeLog.txt so I am not prompted, clear it our after running gen_repos_files.sh
Notes: The changelog.update.txt, is in the same directory as gen_repos_files.sh. An empty changelog.update.txt will run gen_repos_files.sh without updating ChangeLog.txt. The .genrerc is located in the sbopkgs directory.
When making entries to changelog.update.txt the format should be like this:
No NEWLINE is needed at the end. This is what above produces:
Code:
+--------------------------+
Fri Aug 25 11:17:50 UTC 2023
bitcoin-25.0-x86_64-1_SBo: Added.
package-123-x86_64-2_SBo: Rebuilt.
Reason for rebuild.
pacakge-124-x86_64-1_SBo: Upgraded.
You can use gen_repos_files.sh without a gpg key. You will see this message if you don't:
Code:
The GPG private key for "Name <email@address>" wasn't found!
*** packages will not be signed! ***
Continue? [y|N]
If you choose not to use gpg, set STRICTGPG=off on the command line for 'slackpkg update' or or set STRICTGPG=off in slackpkgplus.conf.
Code:
STRICTGPG=off slackpkg update
Here is a search with the first & second methods:
Code:
# slackpkg search bitcoin
Looking for bitcoin in package list. Please wait... DONE
The list below shows all packages with name matching "bitcoin".
[ Status ] [ Repository ] [ Package ]
installed sbopkgs bitcoin-25.0-x86_64-1_SBo
uninstalled(masked) alienbob bitcoin-0.9.1-x86_64-1alien
A listing of the results of gen_repos_files.sh (using gpg):
Code:
# ls -la /home/non-slack/sbopkgs/
total 29032
drwxr-xr-x 2 chris users 4096 Aug 25 19:18 ./
drwxr-xr-x 12 chris users 4096 Aug 25 19:17 ../
-rw-r--r-- 1 chris users 3591 Aug 25 19:00 .genreprc
-rw-r--r-- 1 chris users 1090 Aug 25 19:18 CHECKSUMS.md5
-rw-r--r-- 1 chris users 660 Aug 25 19:18 CHECKSUMS.md5.gz
-rw-r--r-- 1 chris users 1243 Aug 25 19:17 ChangeLog.rss
-rw-r--r-- 1 chris users 187 Aug 25 19:17 ChangeLog.txt
-rw-r--r-- 1 chris users 163 Aug 25 19:18 ChangeLog.txt.gz
-rw-r--r-- 1 chris users 1315 Aug 25 19:18 FILELIST.TXT
-rw-r--r-- 1 chris users 672 Aug 25 19:18 MANIFEST.bz2
-rw-r--r-- 1 chris users 738 Aug 25 19:18 PACKAGES.TXT
-rw-r--r-- 1 chris users 460 Aug 25 19:18 PACKAGES.TXT.gz
-rw-r--r-- 1 chris users 3154 Aug 25 18:41 bitcoin-25.0-x86_64-1_SBo.lst
-rw-r--r-- 1 chris users 693 Aug 25 18:41 bitcoin-25.0-x86_64-1_SBo.meta
-rw-r--r-- 1 root root 29662527 Aug 25 17:53 bitcoin-25.0-x86_64-1_SBo.tgz
-rw-r--r-- 1 chris users 163 Aug 25 19:56 bitcoin-25.0-x86_64-1_SBo.tgz.asc
-rw-r--r-- 1 chris users 64 Aug 25 18:41 bitcoin-25.0-x86_64-1_SBo.tgz.md5
-rw-r--r-- 1 chris users 482 Aug 25 18:41 bitcoin-25.0-x86_64-1_SBo.txt
Of course change the directories to your preferences.
Last edited by chrisretusn; 08-25-2023 at 06:55 AM.
Reason: Corrected a few things.
Blacklisting specific packages is pretty involved so I'll do it later.
Lately, testing slackpkg+-1.9.f-noarch-2mt, I used the following for PKGS_PRIORITY & REPOPLUS: slackpkgplus multilib restricted salixos salixextra slackonly slackers slackers-extra slackers-testing alienbob rlworkman msb.
With this large repository list, after adding salix(extra|os), 'slackpkg upgrade-all' got such a large package list it stopped on package names starting maybe 75% through the alphabet, so didn't have enough space to list the x, xap, xfce series though upgrades for these existed at the time, which after I removed salix(extra|os), then that list completed (and I didn't switch repository list back because Salix stuff I use is now on SlackBuilds.org).
Now 'slackpkg upgrade-all' stopped showing multilib upgrades; only if I 'slackpkg upgrade multilib' will it show those upgrades.
Blacklisting specific packages is pretty involved so I'll do it later.
Lately, testing slackpkg+-1.9.f-noarch-2mt, I used the following for PKGS_PRIORITY & REPOPLUS: slackpkgplus multilib restricted salixos salixextra slackonly slackers slackers-extra slackers-testing alienbob rlworkman msb.
With this large repository list, after adding salix(extra|os), 'slackpkg upgrade-all' got such a large package list it stopped on package names starting maybe 75% through the alphabet, so didn't have enough space to list the x, xap, xfce series though upgrades for these existed at the time, which after I removed salix(extra|os), then that list completed (and I didn't switch repository list back because Salix stuff I use is now on SlackBuilds.org).
Now 'slackpkg upgrade-all' stopped showing multilib upgrades; only if I 'slackpkg upgrade multilib' will it show those upgrades.
Wow, that is a lot of repositories. Love to see your slackpkgplus.conf (Just the applicable parts). This is mine (applicable parts):
I would think there will be a lot of same named packages in this huge mix. Do you actually use packages from all of these repositories? I am willing to duplicate what you have a see what happens here.
[...] Love to see your slackpkgplus.conf (Just the applicable parts).[...] Do you actually use packages from all of these repositories? [...]
Yes. Remember, Robby Workman is also an official Slackware Team mamber so I suggest testing his packages at least if you ever use XFCE. Besides them, I've mostly only seen duplicates with SBo & slackers* (cf), which I rename /var/log/packages/*cf (& etc.) to *_SBo to still get updates and those text files still list the actual source (slackers*/cf or SBo). It can take a lot of time choosing between alienbob, msb (just for eom), rlworkman, SBo, slackers, and (before they hopefully temporarily stopped releasing) slackonly, but this way I get the latest packages from whichever repository is most up-to-date. Years ago I only used to have problems such as mixing vlc & dependencies from SBo & alienbob but that's not so hard to deal with anymore (and he lists dependencies at his homepage on slackware.com).
Well that was fun. Thanks for the configuration. Before I start a few notes about my system.
I have a "full installed" system, upgraded to Thu Dec 21 20:46:11 UTC 2023 in ChangeLog.txt. I am using the development version of slackpkg+ (slackpkg+-1.9.f-noarch-2mt.txz). I have been for a while. I do not build packages from SBo, an exception was I use sbopkg to build bitcoin (not installed) for this testing. I roll my own SlackBuilds. I have a locally synced mirror of slackware64-current using mirror-slackware-current.sh (from Alien Bob) and multilib using rsync via a bash script for current. My alienbob and restricted local repositories only contain the packages I use, 11 and 3 packages respectively using rsync via a bash script. My nonslack (237 packages) repository contains all of my SlackBuilds and resulting packages, all of these are installed. The alienbob, restricted and nonslack repositories are maintained using gen_repos_files.sh (from Alien Bob). My justpkgs (similar to your pkg64-current) is what I use for drop in packages. I have six packages in this one including bitcoin for this testing.
This is the what I have in the slackpkgplus.conf I am using for this testing. I prefer this format of putting each on a separate line for clarity and ease of changing order if needed, plus for adding comments. I don't normally add comments for the MIRRORPLUS entries but did so here.
Code:
# BEGIN PKGS_PRIORITY
PKGS_PRIORITY+=( nonslack ) # My repository.
PKGS_PRIORITY+=( slackware64:kontrast ) # Override slackers.
# PKGS_PRIORITY=( slackpkgplus multilib restricted slackers slackers-extra
# slackers-testing pkg64-current:bitcoin alienbob rlworkman msb )
PKGS_PRIORITY+=( slackpkgplus )
PKGS_PRIORITY+=( multilib ) # My local mirror.
PKGS_PRIORITY+=( restricted ) # My local repository of selected packages I use.
PKGS_PRIORITY+=( slackers )
PKGS_PRIORITY+=( slackers-extra )
PKGS_PRIORITY+=( slackers-testing )
PKGS_PRIORITY+=( justpkgs:bitcoin ) # My local packages in place of pkg64-current:bitcoin.
PKGS_PRIORITY+=( alienbob ) # My local repository of selected packages I use.
PKGS_PRIORITY+=( rlworkman )
PKGS_PRIORITY+=( msb )
# END PKGS_PRIORITY
TAG_PRIORITY=off
# BEGIN REPOPLUS
REPOPLUS+=( nonslack ) # My repository.
#REPOPLUS=( slackpkgplus multilib restricted slackers slackers-extra
# slackers-testing alienbob rlworkman msb )
REPOPLUS+=( slackpkgplus )
REPOPLUS+=( multilib ) # Using my local mirror.
REPOPLUS+=( restricted ) # My local repository of selected packages I use.
REPOPLUS+=( slackers )
REPOPLUS+=( slackers-extra )
REPOPLUS+=( slackers-testing )
REPOPLUS+=( alienbob ) # My local repository of selected packages I use.
REPOPLUS+=( rlworkman )
REPOPLUS+=( msb )
# END REPOPLUS
# BEGIN MIRRORPLUS
# My repository.
MIRRORPLUS['nonslack']=file://home/non-slack/slackbuilds/
#MIRRORPLUS['pkg64-current']=dir://home/d/math/pkg64-current
# My local packages in place of pkg64-current.
MIRRORPLUS['justpkgs']=dir://home/non-slack/justpkgs/
#MIRRORPLUS['multilib']=https://us.slackware.nl/people/alien/multilib/current/
# My local mirror of multilib.
MIRRORPLUS['multilib']=file://home/non-slack/multilib/current/
#MIRRORPLUS['restricted']=https://slackware.nl/people/alien/restricted_sbrepos/current/x86_64/
# My local repository of selected packages I use.
MIRRORPLUS['restricted']=file://home/non-slack/alienbob_restricted/
#MIRRORPLUS['alienbob']=https://us.slackware.nl/people/alien/sbrepos/current/x86_64/
# My local repository of selected packages I use.
MIRRORPLUS['alienbob']=file://home/non-slack/alienbob/
MIRRORPLUS['rlworkman']=https://rlworkman.net/pkgs/current/
#MIRRORPLUS['studioware']=https://slackware.uk/studioware/15.0
#MIRRORPLUS['slackonly']=https://packages.slackonly.com/pub/packages/current-x86_64/
MIRRORPLUS['slackers']=https://slackers.it/repository/slackware64-current/
MIRRORPLUS['slackers-extra']=https://slackers.it/repository/slackware64-current-extra/
MIRRORPLUS['slackers-testing']=https://slackers.it/repository/slackware64-current-testing/
MIRRORPLUS['msb']=https://slackware.uk/msb/current/latest/x86_64/
#MIRRORPLUS['salixos']=https://download.salixos.org/x86_64/15.0/
#MIRRORPLUS['salixextra']=https://download.salixos.org/x86_64/extra-15.0/
MIRRORPLUS['slackpkgplus']=https://slakfinder.org/slackpkg+dev/
SEARCH_SBO=off
SBO['current']=https://cgit.ponce.cc/slackbuilds/
Running 'slackpkg upgrade-all' results in one package showing as needing an upgrade. slackpkg wants to upgrade the installed slackware64:kontrast-23.08.4-x86_64-1 to slackers:kontrast-23.08.3-x86_64-1cf.txz. This is NOT an issue with slackpkg+, this is expected packages identified in slackpkgplus.conf take priority over slackware64. The solution is it add this to slackpkgplus.conf before the slackers entry. It's in bold in the code block above.
Code:
PKGS_PRIORITY+=( slackware64:kontrast )
I would like to note that there are problems with these three MIRRORPLUS entries (you do have then commented out). They are not for current but for 15.0.
With the above slackpkgplug.conf setting I used above I have no issues at all, slackpkg upgrade-all results in no packages to upgrade. The 'slackpkg update' takes longer that I like which is one reason I decided to stay with my local repositories. Also the download of SBo for searching takes a long time on first run or when it needs to be update. I don't use SBo except as a reference (if needed) in building my own SlackBuilds which are not compatible with SBo builds.
Quote:
Originally Posted by dchmelik
Lately, testing slackpkg+-1.9.f-noarch-2mt, I used the following for PKGS_PRIORITY & REPOPLUS: slackpkgplus multilib restricted salixos salixextra slackonly slackers slackers-extra slackers-testing alienbob rlworkman msb.
With this large repository list, after adding salix(extra|os), 'slackpkg upgrade-all' got such a large package list it stopped on package names starting maybe 75% through the alphabet
I got adventurous. I added slalixos, slalixextra and for good measure slackonly.
First observation excluding the 15.0 mentioned above, salixos and salixextra doesn't have a MANIFEST.bz2, not really a problem unless you want to search those repositories. Second observation when running 'slackpkg upgrade-all' there were 135 packages listed for upgrades, most of them from slackonly. During all of this testing, slackpkg worked as expected, it did not stop at any point.
Quote:
Originally Posted by dchmelik
Now 'slackpkg upgrade-all' stopped showing multilib upgrades; only if I 'slackpkg upgrade multilib' will it show those upgrades.
For me even with the above setup for slackpkgplus.conf, multilib upgrades with 'slackpkg upgrade-all', 'slackpkg upgrade multilib' comes up with nothing to upgrade.
I plan to use this configuration for a while just to see if issues develop.
Last edited by chrisretusn; 12-22-2023 at 10:46 AM.
[...]During all of this testing, slackpkg worked as expected, it did not stop at any point.[...]
If you don't have almost 1700+ packages installed from alienbob, multilib, rlworkman, SBo, slackers, you may not see the list fill up when you add salix*... not that it stops, just stops working right.
Quote:
For me even with the above setup for slackpkgplus.conf, multilib upgrades with 'slackpkg upgrade-all', 'slackpkg upgrade multilib' comes up with nothing to upgrade.[...]
Because it wasn't updated at that time; wait until it is.
If you don't have almost 1700+ packages installed from alienbob, multilib, rlworkman, SBo, slackers, you may not see the list fill up when you add salix*... not that it stops, just stops working right.
Because it wasn't updated at that time; wait until it is.
I have 2084 packages installed, 100% of them are upgraded to latest version. I frequently run slackpkg to keep my system up to date.
Just how many packages to you have installed anyway?
Code:
find /var/lib/pkgtools/packages/* | wc -l
Are you aware that rlworkman has no packages in it? From it's ChangeLog.txt:
Code:
Mon Dec 28 07:04:13 UTC 2020
*: Removed.
All of this is now in the stock -current tree, so no need to keep
anything here. I like the way this has been working... :D
I switched alienbob and restricted to a remote URL, same as in your MIRRORPLUS variables. I did a test run using this:
I resulted in 1751 packages to be installed. No issues.
Quote:
Originally Posted by dchmelik
Were some also Slackware updates, and after you added salix*, where did the graphical list end?
There were no Slackware updates, I did an install. With the dialog interface, graphical list I can page go down to the 100% point. I paged up and down, used the arrow keys, home and end thru the list a few times. No issues. Since this is my main computer, I used Cancel to not install 1751 packages.
As for 'slackpkg upgrade-all' I did one earlier today, the was one package from alienbob and one from nonslack (my repo). Tomorrow there will be. My cron job syncs with the slackware64-current mirror at 0515
Quote:
Originally Posted by chrisretusn
I don't understand why the salixos, salix-extra, why?
Quote:
Originally Posted by dchmelik
I wanted to try a few packages. Most are on SBo now.
Makes sense. If I want to try a package I just download it and put them my justpkgs repo (MIRRORPLUS['justpkgs']=dir://home/non-slack/justpkgs/). Most of the time I just create a SlackBuild in put the resulting package in my nonslack repository.
Quote:
Originally Posted by chrisretusn
How do you handle your SBo packages? How many of those do you have installed?
Quote:
Originally Posted by dchmelik
Occasionally manually, and otherwise with sbopokg, sbotools, SlackOnly, etc.
I have zero SBo packages installed; slackware64-1626, cgs-181, alien-27, compat32-247, mt, me and salix15.0 1 each. My SlackBuilds are all have the cgs tag. I do have sbopkg and slpkg installed. Mostly to play with. I used sbopkg to build the bitcoin package. It's still in my justpkgs repo.
I don't understand why the salixos, salix-extra, why?
I wanted to try a few packages. Most are on SBo now.
Also since almost the time slapt-get started, I wanted to learn that and all package tools for Slackware including (not just managing but information, building/maintaining, etc.) that and other Salix ones, such as gslapt, slapt-src, sourcery, spi, spkg... one or more of these had quite a few dependencies in the Salix repository, and I was trying to figure out how to use that without messing things up since Slackware 15 and earlier stable versions since mid-'0s. Many/most Slackware 15 packages seem to work fine on Slackware-current (of course I wouldn't use an older aaa* package or something) so that's why I still had those in there, but commented it out when the whole list didn't show up. I guess you'd have to have an upgrade list in slackpkg+ almost as large as Slackware itself before the list ran out of space...
Also since almost the time slapt-get started, I wanted to learn that and all package tools for Slackware including (not just managing but information, building/maintaining, etc.) that and other Salix ones, such as gslapt, slapt-src, sourcery, spi, spkg... one or more of these had quite a few dependencies in the Salix repository, and I was trying to figure out how to use that without messing things up since Slackware 15 and earlier stable versions since mid-'0s. Many/most Slackware 15 packages seem to work fine on Slackware-current (of course I wouldn't use an older aaa* package or something) so that's why I still had those in there, but commented it out when the whole list didn't show up. I guess you'd have to have an upgrade list in slackpkg+ almost as large as Slackware itself before the list ran out of space...
Thanks! I've done much the same, playing around, testing some those same packages tools for Slackware. In the end I have settled with slackpkg with the slackpkg+ plugin. I build my own because I find often the SBo build does not match was I want. My SlackBuild scripts do things you cant do with SBo and my build environment it difference that SBo's.
Your last sentence... I just tried in a virtual machine to install a massive number of packages, 8420 of them. All went well, the dialog list came up just fine I was able to navigate up and down through the entire list of 8420 packages no problem. So I went ahead with the install. The hard disk was 64 GB in size, I ran out of disk space. The was only 25% of the disk being used before I started.
Going to go with a bigger disk on my next try.
Last edited by chrisretusn; 12-23-2023 at 09:43 PM.
[...]Your last sentence... I just tried in a virtual machine to install a massive number of packages, 8420 of them. All went well, the dialog list came up just fine I was able to navigate up and down through the entire list of 8420 packages no problem. So I went ahead with the install. The hard disk was 64 GB in size, I ran out of disk space. The was only 25% of the disk being used before I started.
Going to go with a bigger disk on my next try.
If what happened to me was a limitation with slackpkg or slackpkg+ rather than something went wrong with one of those, with this many you'd have seen it (unless it has to do with number of repositories that update at a time including stable Slackware, multilib, anything else not updated recently). I guess it generally doesn't happen to others so I need to reinstall/reconfigure both... but I may be waiting until stable Slackware 15.1 until trying to install extra Salix package tools from slackpkg+ again...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
part of my slackpkgplus.conf
The was only 25% of the disk being used before I started.
