LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
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 04-26-2010, 10:31 PM   #1
damgar
Senior Member
 
Registered: Sep 2009
Location: dallas, tx
Distribution: Slackware - current multilib/gsb Arch
Posts: 1,949
Blog Entries: 8

Rep: Reputation: 201Reputation: 201Reputation: 201
Slackpkg, running current and multilib, do the compat32 files need to be blacklisted?


I am trying to make certain of what needs to be blacklisted for slackpkg to safely be used to upgrade my current box, without breaking multilib. The only reference to blacklisting on Alien Bob's site is:
Quote:
If you use a package manager like slackpkg you will have to add all glibc and gcc package names to its package blacklist. If you do not take this precaution, you run the risk of your package manager accidentally replacing your multilib versions with Slackware's original pure 64-bit versions!
I've blacklisted the gcc/glibc packages, as well as the 32 bit programs I run, but I'm not sure what to do about the compat32 files. Will slackpkg skip these files or will they be removed and replaced with 64 bit packages?
 
Old 04-27-2010, 02:11 AM   #2
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,257

Rep: Reputation: Disabled
Quote:
Originally Posted by damgar View Post
I'm not sure what to do about the compat32 files. Will slackpkg skip these files or will they be removed and replaced with 64 bit packages?
THose "compat32" packagess have original names, they will not be seen by slackpkg when you run "slackpkg upgrade-all". Only if you run "slackpkg clean-system" will slackpkg offer to remove these packages since they are not original Slackware packages.

So, blacklisting the gcc and glibc packages would be enough.

Eric
 
Old 04-27-2010, 07:43 AM   #3
damgar
Senior Member
 
Registered: Sep 2009
Location: dallas, tx
Distribution: Slackware - current multilib/gsb Arch
Posts: 1,949
Blog Entries: 8

Original Poster
Rep: Reputation: 201Reputation: 201Reputation: 201
Thank you for the clarification.
 
  


Reply


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
slackpkg/blacklist for AlienBob's current multilib and kde 4.4.2 packages damgar Slackware 7 04-08-2010 09:33 PM
slack64-current multilib slackpkg upgrade portia Slackware 4 01-05-2010 02:47 PM
Blacklisting gcc/glibc with slackpkg in multilib-current damgar Slackware 1 01-04-2010 11:15 PM
[SOLVED] -current, multilib, and KDE-4.3.4 mlangdn Slackware 12 12-23-2009 03:57 AM
Insomnia 0, 64-Current+Multilib 1 trxdraxon Slackware 2 12-22-2009 02:01 AM


All times are GMT -5. The time now is 04:49 AM.

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