slackware current and slackpkg selects kdei packages series in error
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.
slackware current and slackpkg selects kdei packages series in error
This has been an issue with current beta, RC1 and now RC2 on both x86 archs. when using slackpkg to update, even though series kdei was NOT elected during the initial installation, executing
slackpkg install-new
slackpkg upgrade-all
all the calligra-l10n-* languages are selected. Nothing else from series kdei and nothing from emacs, which I also did not install.
I can blacklist this; however, isn't this supposed to be automagical? Why just calligra and not any other packages/series I skipped? This also occurs in the qemu VMs when I do a full install omitting just /kdei
Nope, did it again: this time slackware64-14-RC2 updated from beta pre-RC1. No matter what (short of blacklisting), slackpkg thinks the kdei/calligra-l10n-* files need to be added when given "slackpkg install-new" - Note that there are a bunch of otehr files kdei/ that slackpkg properly ignores.
Nope, did it again: this time slackware64-14-RC2 updated from beta pre-RC1. No matter what (short of blacklisting), slackpkg thinks the kdei/calligra-l10n-* files need to be added when given "slackpkg install-new"
Yes. I see the same behaviour when I issue slackpkg install-new.
You may not realize how slackpkg determines if a package is new to Slackware.
The "slackpkg install-new" command acts on the word "Added" in the Slackware ChangeLog.txt. So, if you upgrade to a certain Slackware release, slackpkg will scan that release's ChangeLog.txt and add all packages to the pick-list for which it finds "Added."
That is why you get things like gptfdisk, but also all the calligra-l10n packages when you run "slackpkg install-new" for slackware-current.
Slackpkg does not look at tagfiles at all. And inide the Slackware installer, you can simply de-select the KDEI series.
Eric
Hi Eric, Thanks for the reply.
Do you have an idea why these few kdei packages should default to "on" while all others default to "off"? I Always remove them during menuconfig and got no system break down in any way.
I see slackpkg as a more or less default "on" with Slackware (official) packages when it comes to updating. If I want to turn something off, that is what blacklist is for. When I saw that calligra was added, I turned to blacklist. Originally I used "calligra-l10n", then decided since I don't use kdei at all, I when with "./slackwar64[0-9]+/kdei"
If I needed a particular language file I would have done this differently in my blacklist
When Slackware 14.0 is released, I would no longer need those entries.
Using slakcpkg search is a good way to test blacklist entries. Also looking at /var/lib/slackpkg/pkglist can give you ideas on what you can use in search and in blacklist.
Last edited by chrisretusn; 08-17-2012 at 10:45 PM.
Reason: Add last sentence
You may not realize how slackpkg determines if a package is new to Slackware.
The "slackpkg install-new" command acts on the word "Added" in the Slackware ChangeLog.txt. So, if you upgrade to a certain Slackware release, slackpkg will scan that release's ChangeLog.txt and add all packages to the pick-list for which it finds "Added."
That is why you get things like gptfdisk, but also all the calligra-l10n packages when you run "slackpkg install-new" for slackware-current.
Eric
Hmmm...that makes sense from one point, but not in another, as just searching for "added" is a bit of a short cut. Why, once 'install-new' is run and new packages added, why do just 'calligra-l10n' packages come back again after each update? Heck, the where added April 14, 2012. I kipped other packages and series while I'm playing around in a VM. Should not slackpkg skip a package series if it was not installed originally? Should not slackpkg skip scanning for the added packages if the user unchecks the box?
Well, my opinion. Guess I could patch it if it bothers my enough....
I had thought about what you just posted and for most people it would work but not all.
If for instance you want to upgrade only part of the system first and then the rest later on the second run you might end up missing something.
What it probably needs is a bit more intelligence in it to detect which packages out of the entire system are missing and provide them via another option like "slackpkg install-missing"
What it probably needs is a bit more intelligence in it to detect which packages out of the entire system are missing and provide them via another option like "slackpkg install-missing"
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
slackware current and slackpkg selects kdei packages series in error
