LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 08-18-2012, 06:25 AM   #16
chrisretusn
Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware
Posts: 489

Rep: Reputation: Disabled

Quote:
Originally Posted by kingbeowulf View Post
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?
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.

Quote:
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?
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.

Quote:
Should not slackpkg skip scanning for the added packages if the user unchecks the box?
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.
Old 08-18-2012, 07:12 AM   #17
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,333

Rep: Reputation: Disabled
Quote:
Originally Posted by kingbeowulf View Post
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....
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.
Old 08-18-2012, 07:20 AM   #18
guanx
Senior Member
 
Registered: Dec 2008
Posts: 1,014

Rep: Reputation: 146Reputation: 146
Quote:
Originally Posted by chrisretusn View Post
Why isn't it? Adding kdei to blacklist prevents all of the kdei series packages from being acted on. This takes care of the caligra-l10n packages.
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.
 
Old 08-18-2012, 08:07 AM   #19
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 2,594

Rep: Reputation: 435Reputation: 435Reputation: 435Reputation: 435Reputation: 435
using capital letters will not help solving your problems
 
Old 08-18-2012, 08:21 AM   #20
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,333

Rep: Reputation: Disabled
Quote:
Originally Posted by guanx View Post
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.
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
 
Old 08-18-2012, 11:23 AM   #21
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 3,485

Rep: Reputation: 856Reputation: 856Reputation: 856Reputation: 856Reputation: 856Reputation: 856Reputation: 856
Quote:
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.
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.
 
Old 08-18-2012, 11:38 AM   #22
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 875

Rep: Reputation: 1819Reputation: 1819Reputation: 1819Reputation: 1819Reputation: 1819Reputation: 1819Reputation: 1819Reputation: 1819Reputation: 1819Reputation: 1819Reputation: 1819
Quote:
Originally Posted by guanx View Post
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.
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.
 
Old 08-18-2012, 12:00 PM   #23
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,333

Rep: Reputation: Disabled
Quote:
Originally Posted by allend View Post
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.
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
 
Old 08-18-2012, 12:25 PM   #24
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 3,485

Rep: Reputation: 856Reputation: 856Reputation: 856Reputation: 856Reputation: 856Reputation: 856Reputation: 856
I stand corrected. Please accept my apologies for my lack of understanding and thankyou for correcting my error.
 
Old 08-18-2012, 01:58 PM   #25
wadsworth
Member
 
Registered: Aug 2007
Distribution: Slackware64 13.37
Posts: 215

Rep: Reputation: 65
Code:
slackpkg install slackware64
would give you a list of all packages not already installed.
 
Old 08-18-2012, 03:12 PM   #26
kingbeowulf
Member
 
Registered: Oct 2003
Location: WA
Distribution: Slackware64 14.1, Slackware 14.1
Posts: 526

Original Poster
Rep: Reputation: 140Reputation: 140
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.
 
Old 08-18-2012, 04:09 PM   #27
hitest
Senior Member
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, OpenBSD
Posts: 4,241

Rep: Reputation: 571Reputation: 571Reputation: 571Reputation: 571Reputation: 571Reputation: 571
Quote:
Originally Posted by kingbeowulf View Post
Sorry for wasting time with it. I really should not post stuff at midnight after a long day a and a few beers!
I do some of my best and worst work after several malt beverages. Thanks for the explanation, Eric.
 
Old 08-19-2012, 11:14 AM   #28
chrisretusn
Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware
Posts: 489

Rep: Reputation: Disabled
Quote:
Originally Posted by kingbeowulf View Post
TSorry 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 was not wasted time, a lot of good things said in this thread. Make us all smarter.
 
  


Reply

Tags
slackpkg, tagfiles, upgrade


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] [Slackware 13.1 and upcoming 13.2] tagfiles wrong for kdei package series? titopoquito Slackware 4 01-13-2011 12:59 PM
slackpkg/blacklist for AlienBob's current multilib and kde 4.4.2 packages damgar Slackware 7 04-08-2010 10:33 PM
Slackware current slackpkg problem LordAnta Slackware 6 10-10-2009 07:15 AM
Slackpkg slackware current-64 bit todders Slackware 7 07-15-2009 07:00 PM
slackpkg update = slackware-current? trashbird1240 Slackware 2 04-24-2007 09:50 AM


All times are GMT -5. The time now is 06:13 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration