The calligra-l10n packages keep coming back because you have not installed them yet. If you were to install them they would not show up when you run "slackpkg install-new". The install-new action installs new packages that have been added to the official Slackware package set since Slackware 13.37 was released. Those calligra language files are some of those new packages. If you do not want to install them, then you have to blacklist them. At least until Slackware 14.0 is released. When Slackware 14.0 is release a new ChangeLog.txt will be started for that version.

Slackware 13.37 was released Mon Apr 25 13:37:00 UTC 2011, That is the first entry in the Slackware 13.37 ChangeLog.txt, "slackpkg install-new" scans ChangeLog.txt for new packages since the release. Any package marked as added will show up. This included packages for series you have not installed. So if a new language package is added to Slackware for kde, that package will show up when using the install-new action.

The recommend and default install for Slackware is Full Install, this installs everything except the kdei series. If you choose to do something else, then it is up to you.The slackpkg blacklist was provided for that reason. It also serves to keep non-Slackware packages from showing up when using the clean-system action.

Is does, for that instance. Your selection are not saved. That is just a simple GUI interface to allow users to select or deselect packages. I don't use that interface, I have DIALOG=off in my slackpkg.conf, I simply get a list and a Y/n question at the end. If I see something I don't want added such as the calligra language packages, I answer No and blacklist them, then run slackpkg again.

2 members found this post helpful.

You are using slackpkg in ways it is not meant to be used. It is not meant as a tool to keep up to date with -current (although it does a better job at that than any other means I know of). Its original purpose was mainly to serve as a dependable tool to upgrade between stable releases and to make it easier to install or upgrade parts of Slackware (again, assuming you are running a stable release).

That is why the "install-new" works as it does. It scans for packages that are new to Slackware in the release you are working with... not packages that would be new to your computer.

If you were to improve the slackpkg tool, I would like to see an addition of something like "slackpkg install-missing" where I would be presented with a list of all the packages which are part of Slackware but which I have not installed yet, for whatever reason. And taking into account the blacklist of course so that I would never have to see any package from the KDEI series for instance.

I know that the slackpkg developer(s) are busy in real life and that is a reason why no new functionality has been added for quite some time.

Eric

1 members found this post helpful.

Maybe I should start a new thread ... but wait -- I've already started a thread for this long long ago.

I am simply asking --

WHY ACROSS SEVERAL MAJOR RELEASES THE "kde-l10n-ca@valencia", "kde-l10n-ia", "kde-l10n-id", AND "kde-l10n-si" PACKAGES ARE KEPT SELECTED BY DEFAULT AND ALL THE OTHERS UNSELECTED.
WHY IS THIS ANNOUNCES FIXED YET UNCHANGED (THIS IS WHAT CONFUSES ME MOST).
WHAT IS THE IMPORTANCE OF THESE LOCALES TO SLACKWARE.

Thanks.

using capital letters will not help solving your problems

OK. Let's do one step back. Or a few even.

Are you talking about a bug in the Slackware installer, or in slackpkg?
Can you describe in detail where you experience this?
What was the LQ thread where you addressed this issue?
Where was it declared "fixed"?

Those locales are of course not important at all to Slackware, only to the people using those languages. But I have not yet come across a situation where those locales were selected and others were not. That is why I want you to be more specific.

Eric

That is exactly what 'slackpkg install-new' does.

The equation is simple - Packages offered by 'slackpkg install-new' = (Packages in official tree not already installed) - (Packages that are blacklisted)

There is no problem with Slackware or slackpkg. It merely requires intelligent use of /etc/slackpkg/blacklist.

Ow, my ear.

I believe that it is fixed, really! The maketag script was changed a week ago to default everything to off. And I have no idea why those four locales had been set to default to on before.

No, that is not what "slackpkg install-new" does.
Simple test: removepkg any package which was already present in a previous release of Slackware. Say, "libgpod". After you removed it, run "slackpkg install-new". Does libgpod show up in the list of packages to install? No, it does not.

The "slackpkg install-new" command is triggered by the word "Added." next to a package name, in the ChangeLog.txt of the Slackware release it was configured to use.

Eric

I stand corrected. Please accept my apologies for my lack of understanding and thankyou for correcting my error.

would give you a list of all packages not already installed.

Thanks, Alien BOB and chrisretusn,

I rescind my slackpkg rant and stand corrected. If it weren't a decent tool I wouldn't use it. The correct way would be to make better use of the blacklist to find tune what packages I want while experimentng with -current.

Sorry for wasting time with it. I really should not post stuff at midnight after a long day a and a few beers! Now, after sleep, coffee, as I read over the comments, I see I was confused, as were a few others.

I do some of my best and worst work after several malt beverages. Thanks for the explanation, Eric.

I was not wasted time, a lot of good things said in this thread. Make us all smarter.