On Wednesday 25 October 2006 22:49, Michel Salim wrote:
Having 32-bit libraries makes sense, for the purpose of running legacy closed-source applications. Having i386 -devel packages... does not. What's the point, without a 32-bit compiler to go along?
The point is to be able to develop 32bit applications. 64bit gcc can create 32 bit binaries. -m32.
And then there are the i386 applications: firefox, gaim, etc. These get installed by default (there's no way I can see to exclude i386 packages short of using kickstart). Removing them should be straightforward, right? Just yum --remove glibc.i686. But it's not that simple:
These are showing up because they have a -devel subpackage, and the -devel subpackage is what we key off of to make it multilib. -devel requires its arch specific library (usually main) package.
As far as removing, yum remove *.i?86
Works for me every time. The only shared files that may get removed are documents (bug that needs to be fixed but not critical)
- Often times, removing a 32-bit package also removes the files
shared with the 64-bit sibling. 2. With the default FC6 install, I get a circular dependency when trying to remove glibc.i686. It never displays the final list of affected packages.
Again, try: yum remove *.i?86