Hi all, I'm a member of the Gentoo/AMD64 team which is working hard on getting true multilib support. The problem is that we have some issues with colliding files, and therefore I thought it would be wise to look how other distros solve these problems. So, if you could answer the few following questions I would be very thankful :) 1. Take a package that provides both libraries and binaries. Install it both 64bit and 32bit. How are the conflicting files in /usr/bin (well, anything in PATH) handled? Do you simply end up with having whatever was first/latest installed or is 64bit preferred over 32bit or vice versa? 2. What happens when you try to uninstall said package 64bit-wise? Are the binaries in /usr/bin left there or removed? 3. Same as question 2 but regarding 32bit -- Kind Regards, Simon Stelling Gentoo/AMD64 Developer
On Sunday 12 March 2006 14:57, Simon Stelling wrote:
I'm a member of the Gentoo/AMD64 team which is working hard on getting true multilib support.
Great. Finally doing the right thing.
Normally rpm doesn't allow duplicated files. There are a couple of ways to handle it: - You use special compat packages for the 32bit libraries that don't contain anything in $PATH or in /usr/include, only libraries That is what the core SUSE distribution does. This avoids the problem completely. - You can overwrite the duplicate check with --force. Then the latest wins.[I suspect a lot of people do that for third party rpms]. It's a bit unclean though because it makes the rpm database inconsistent. - Better: you can filter out some paths during rpm installation using --excludepath. With that it is possible to tell rpm to just not i nstall the wrong bins. So e.g. to get just the libraries you would typically exclude */include and */bin -Andi
On Sunday 12 March 2006 14:57, Simon Stelling wrote:
I'm a member of the Gentoo/AMD64 team which is working hard on getting true multilib support.
Great. Finally doing the right thing.
Normally rpm doesn't allow duplicated files. There are a couple of ways to handle it: - You use special compat packages for the 32bit libraries that don't contain anything in $PATH or in /usr/include, only libraries That is what the core SUSE distribution does. This avoids the problem completely. - You can overwrite the duplicate check with --force. Then the latest wins.[I suspect a lot of people do that for third party rpms]. It's a bit unclean though because it makes the rpm database inconsistent. - Better: you can filter out some paths during rpm installation using --excludepath. With that it is possible to tell rpm to just not i nstall the wrong bins. So e.g. to get just the libraries you would typically exclude */include and */bin -Andi
participants (2)
-
Andi Kleen -
Simon Stelling