LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   slack-14.0 UPGRADE.TXT & compat32 (http://www.linuxquestions.org/questions/slackware-14/slack-14-0-upgrade-txt-and-compat32-4175430328/)

business_kid 10-03-2012 01:48 PM

slack-14.0 UPGRADE.TXT & compat32
 
This is not a query.
Can I request an update of this for the next release to cater for the 64bit multilib scenario where this bit

#!/bin/sh
for dir in a ap d e f k kde l n t tcl x xap xfce y ; do
( cd $dir ; upgradepkg --install-new *.t?z )
done

can easily upgrade compat32 packages (and has!), leaving 64 bit ones in place, and something similar to install compat32 packages can upgrade 64 bit packages.

Alien Bob 10-03-2012 02:10 PM

Slackware does not ship with any multilib packages, therefore it makes no sense to include a multilib upgrade scenario in Slackware's UPGRADE.TXT.

Furthermore, it looks like you are claiming that upgrading a "compat32" package can overwrite a 64-bit package? That would not be possible, since no "compat32" package carries the name of a 64-bit package and vice versa.

Eric

business_kid 10-04-2012 03:32 AM

No a compat32 package will not overwrite a 64 bit package under normal applications. Names are different. But with 'upgradepkg *.t?z' the first similar package is chosen. I upgraded (64 bit only) and lost the use of wine, and traced it to all the basic libs missing because they had been uninstalled. Then when I went to install them with a wildcard, they started overwriting 64 bit packages. I stopped that at once, however, and straightened things out.

The specific section of upgrade.txt that I quoted is no longer good enough. That's all I'm saying. I was thinking of a variable for the package and a 'grep -v compat32' in there but my scripting doesn't reach to it.


All times are GMT -5. The time now is 08:57 PM.