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.
slackpkg+-1.7.0-noarch-10mt.txz and slackpkg+-1.7.0d1-noarch-6mt.txz now allow to use new blacklist system, but only for install/upgrade/remove options (not search) and not for greylist.
Perfect! Thanks! I've been holding off on testing the slackpkg beta. I have installed slackpkg-2.84.0_beta3-noarch-1_rlw and slackpkg+-1.7.0-noarch-10mt, no issues so far.
This is the program that comes with Slackware that does things like...
Code:
pkgtool
or
Code:
installpkg
etc, correct?
No, it's the program that does things like:
Code:
slackpkg update
slackpkg install-new
slackpkg upgrade-all
etc.
It is a higher-level package management tool that downloads packages from a mirror, checks whether packages in your system are in need of upgrades, and other stuff like that.
- this leads to 2.84.0 ; notable changes include a backwards-incompatible
fix for blacklisting entire package sets. I would have preferred to
not do that (break back-compat), but this new syntax allows everything
we previously allowed and then some. Major changes are:
- Use CHECKSUMS.md5.asc to determine ChangeLog newness
- In doinst.sh, don't remove ChangeLog.txt upon upgrade/reinstall.
- In doinst.sh, remove /var/lib/slackpkg/CHECKSUMS* when slackpkg
itself is upgraded
- Fix for /var/log/packages/ possibly being a symlink to elsewhere
- Catch errors and return exit status 1 if they occur
- Add support for listing .new files without PAGER
- Add config option to allow *not* saving .orig configs
- Mention possible stale mirror if CHECKSUMS.md5 gpg verify fails
- Removed bjtu.edu.cn and switch.ch mirrors
- Allow blacklisting of individual packages without collateral
damage (e.g. glibc ---> glibc-*). This changes the prior behavior
of the blacklist function; previously, adding "glibc" to the
blacklist would cause glibc, glibc-profile, glibc-zoneinfo, et al
to be ignored by slackpkg. The new behavior is that *only* the
glibc package is ignored. If you want to blacklist all packages
whose names begin with glibc, you would need to add "glibc.*" to
the blacklist now. Also note that any special characters, e.g. "+",
will need to be escaped in the blacklist file.
- Fix support for blacklisting entire package sets; blacklisted sets
now need a trailing slash, e.g. kde/
Good question. That's clearer in the https://slackpkg.org/beta/ChangeLog link -- the text I quoted in the post here is a summary of cumulative changes since 2.83.0.
However, enhancement and fixing of existing functionality *is* desirable.
My suggestion for an enhancement is to add the date to the default cache path in slackpkg.conf.
Code:
TEMP=/var/cache/packages$(date +%Y%m%d)
The change would make no difference to anyone with the default of DELALL=on.
However, with DELALL=off, a directory with the date appended is created. This makes keeping a local archive easier. Also, the directory can be copied to one or more other machines, so that slackpkg can be run without needing to again download packages from the internet.
I had used slackpkg+ before and everything worked fine except slackpkg check-updates.
Interestingly, the error is in the repositories of AlienBob and slackpkgplus itself, even after slackpkg update gpg.
My suggestion for an enhancement is to add the date to the default cache path in slackpkg.conf.
Code:
TEMP=/var/cache/packages$(date +%Y%m%d)
The change would make no difference to anyone with the default of DELALL=on.
However, with DELALL=off, a directory with the date appended is created. This makes keeping a local archive easier. Also, the directory can be copied to one or more other machines, so that slackpkg can be run without needing to again download packages from the internet.
As much as I can relate to the desire for a local archive, I don't like the idea of putting the date in there. I *might* be inclined to make a $date_like subdirectory in /var/cache/packages/ and store stuff there, but for the most part I think the "local archive" problem is better served elsewhere, i.e. rsync to a local directory and point slackpkg there.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
