LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Slackpkg, running current and multilib, do the compat32 files need to be blacklisted? (http://www.linuxquestions.org/questions/slackware-14/slackpkg-running-current-and-multilib-do-the-compat32-files-need-to-be-blacklisted-804416/)

damgar 04-26-2010 11:31 PM

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?

Alien Bob 04-27-2010 03:11 AM

Quote:

Originally Posted by damgar (Post 3948811)
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

damgar 04-27-2010 08:43 AM

Thank you for the clarification.


All times are GMT -5. The time now is 04:45 PM.