Quote:
Quote:
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. Quote:
|
Quote:
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 |
Quote:
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
|
Quote:
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 |
Quote:
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. |
Quote:
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. |
Quote:
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.
|
Code:
slackpkg install slackware64 |
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. |
Quote:
|
Quote:
|
All times are GMT -5. The time now is 02:00 AM. |