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.
I'm wondering if slackpkg is still up to date. I looked through slackpkg scripts installed into my -current and found that it still uses /var/log/packages (mostly in /usr/libexec/slackpkg/core-functions.sh, but also in functions.d/). Well, of course one can create a symlink to /var/lib/pkgtools/packages, and it perfectly works, but personally I don't think this is a good way to resolve the problem, it must be in some way consistent with pkgtools. I see that the latest update of the stable version of slackpkg was in 2018, and even according to the beta changelog the /var/log path is mentioned only once since the last stable release:
> - Fix for /var/log/packages/ possibly being a symlink to elsewhere
so it still relies on the "old" path.
P.S. I tried to change the core-functions.sh script by `%s/\/var\/log\/packages/${PKGDIR}/g`, but it was too simple to resolve the problem.
P.P.S. I use Slackware just for one week and really enjoy it despite troubles I needed to fix.
It was pretty clear to me. He is saying that slackpkg on -current still has references to the deprecated /var/log/packages and /var/log/scripts directories.
It was pretty clear to me. He is saying that slackpkg on -current still has references to the deprecated /var/log/packages and /var/log/scripts directories.
but is it actually a problem? IMHO it's not as it doesn't break anything.
it could be actually a choice for backward compatibility.
but is it actually a problem? IMHO it's not as it doesn't break anything.
it could be actually a choice for backward compatibility.
It doesn't break anything here, since by default /var/log/packages and /var/log/scripts are symlinked to the appropriate directories. I read it more as a notice, with the OP assuming it was an oversight. But you're right, it could be intentional.
I'm sorry but from your post isn't very clear what the problem is... what is not working there?
Thanks!
My problem was during the fresh install of 14.2 and then "blind" upgrade to -current the symlink wasn't automatically created. Well, on the one hand this is my fault, but on the other hand I'm afraid it can create problems in future.
but is it actually a problem? IMHO it's not as it doesn't break anything.
it could be actually a choice for backward compatibility.
I assume it is fine as soon as this is written in the slackpkg documentation explicitly. Although, I personally dislike the usage of hard-coded path withing the scripts.
I personally dislike the usage of hard-coded path withing the scripts.
Slackpkg's are the defaults and can be overridden -- see the $WORKDIR as set in /etc/slackpkg/slackpkg.conf and the $ROOT and $CONF as "inherited" from the pkgtools.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.