new pkgtool location /var/lib/pkgtools for inxi -r slackware
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.
new pkgtool location /var/lib/pkgtools for inxi -r slackware
I've been tying up some loose ends etc and just learned that slackware 15 is going to move its package location from /var/log/packages to /var/lib/pkgtools
Can someone confirm or deny that the new location will function the same, that is, that directory will contain the installed package files? Currently inxi just reads /var/log/packages and counts up what it found inside to complete the pkgtool: counts for -I line, or -r line. In other words, is this simply a move of the location of the main package info directory and no other changes?
I have this coded out in pinxi already, but just wanted to confirm that this assumption is correct.
I've been tying up some loose ends etc and just learned that slackware 15 is going to move its package location from /var/log/packages to /var/lib/pkgtools
Can someone confirm or deny that the new location will function the same, that is, that directory will contain the installed package files? Currently inxi just reads /var/log/packages and counts up what it found inside to complete the pkgtool: counts for -I line, or -r line. In other words, is this simply a move of the location of the main package info directory and no other changes?
I have this coded out in pinxi already, but just wanted to confirm that this assumption is correct.
/var/log/packages is now a symlink to new location. /var/lib/....
Tue Jun 19 22:35:25 UTC 2018
testing/packages/pkgtools-15.0-noarch-20.txz: Rebuilt.
This update is a bit scarier than usual, so we're going to test it here
first and then move it into the main tree in a couple of days if there
are no serious bug reports. It's well-tested here, and works with the
slackpkg that's in -current now, but I don't know about slackpkg+ so that's
another reason to let it cool down here first. The purpose of this update
is to migrate the package database and directories from /var/log to
/var/lib/pkgtools. /var/log was never a good place for this data, as it is
considered by many to be a directory that could be wiped to free up some
space. Originally the package database was in /var/adm, but the FSSTND
(later FHS) group decided that directory should be a symlink to /var/log,
and I went along with that since it was years ago and I was a n00b and didn't
know any better. /var/lib/pkgtools will be a better and safer location.
The removed_packages and removed_scripts directories are really just logs
that aren't actually used for anything - those will remain under /var/log,
but moved into /var/log/pkgtools. Everything under /var/log will be
considered potentially non-permanent by the pkgtools - if any directories or
symlinks disappear from there, the pkgtools will automatically recreate them
as needed. In fact, the migration process will create symlinks from all the
old directory locations to the new ones, so anything that expects the old
locations (including slackpkg, for now) should continue to work. Once this
moves into the main tree, the plan is to fix other packages to use the new
installer script directory (/var/lib/pkgtools/setup) and change the installer
and slackpkg to use the new native locations for everything. When slackpkg
is changed over to use the new native locations, I'll also make sure to float
that in testing/ for a few days before moving it to the main tree to avoid
more unintentional disruption to slackpkg+ users.
Be aware that the package database migration is a one-way operation, but even
so if you later downgrade to an older version of the pkgtools it will still
work through the compatibility symlinks.
Code:
Thu Jun 21 22:58:42 UTC 2018
a/pkgtools-15.0-noarch-20.txz: Rebuilt.
Move pkgtools database to /var/lib/pkgtools/.
Move removed logs to /var/log/pkgtools/.
Last edited by chrisretusn; 02-13-2021 at 04:47 AM.
Reason: Forgot the dates
Oh, if /var/log/packages is now symbolic link to /var/lib/pkgtools inxi doesn't have to change anything, which is even better. Thanks for confirming. However, it sounds like they may get rid of the sym links once everything is solid, so probably best to use my fix anyway, which is, test for /var/lib/pkgtools directory, if exists, use it instead of legacy /var/log/packages, otherwise don't.
Ah, I'm glad I asked, so the public messages about this change are actually not right I believe. I was wondering why all the packages were being tossed directly into pkgtools/ and not into a sub directory. Thanks for following up.
These changes are in pinxi now if you want to test that it's working as expected. (wget -O pinxi smxi.org/pinxi && chmod +x pinxi && pinxi -ra :: or: pinxi -U if pinxi is already installed)
Ah, I'm glad I asked, so the public messages about this change are actually not right I believe. I was wondering why all the packages were being tossed directly into pkgtools/ and not into a sub directory. Thanks for following up.
Guess depends on how you read it. Prior to this update, there was no /var/lib/pkgtools/ directory. "The purpose of this update is to migrate the package database and directories from /var/log to /var/lib/pkgtools." The database being the /var/log/ subdirectoies packages/, removed_packages/, removed_scripts/, scripts/ and setup/. The migration created a /var/lib/pkgtools/ and /var/log/pkgtools/ directories. The packages/, scripts/ and setup/ directories in /var/log/ were moved to /var/lib/pkgtools/. The removed_packages/ and removed_scripts/ directories were moved to /var/log/pkgtools/. Symlinks were added to maintain compatibility in the event of downgrading to an older version of pkgtools.
Quote:
These changes are in pinxi now if you want to test that it's working as expected. (wget -O pinxi smxi.org/pinxi && chmod +x pinxi && pinxi -ra :: or: pinxi -U if pinxi is already installed)
inxi should work since the symbolic links are in place and would give the same end result while they remain there, but I like to be ahead of the game so if they go away, next inxi will still work fine for slackware.
I just need to tweak the testing a bit more so it's not as hackish, but won't impact the outcomes.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.