32-bit version of every 64-bit package on system?
Subject pretty much says all.
I've run yumex and noticed that there's two copies of nearly every update available for the system. At a glance, I'm seeing both a 32-bit and 64-bit version for evolution, evolution-data-server, and gkhtml3. I know there should be a 32-bit version for some packages, but why would I need two versions of, say, Evolution? |
The quick answer is that you don't. I use a 64 bit computer, so I get (modest) performance boosts from using 64 bit software, hence the 64 bit version. On my second computer, however, I only have a 32 bit processor, so it cannot run 64 bit software, so for it I need the 32 bit.
We could all get by using only 32 bit, but the 64 is there for people who can take advantage of it. You really should only use one on any given computer. |
Yeah that's exactly the thinking behind using the 64-bit distro--that's why I installed it.
Yet, I'm not the one putting the 32-bit packages on there. They're there by default, and that's what's bothersome. |
Oh, I think I understand your question now. You just mean, why do they mix the two together in the repositories? Well, some packages are only available in x86 and not x86_64, and other I guess they just don't want to duplicate where they host the files. By default, yum installs the packages which match your architecture.
|
Wellll... close. :)
Mainly, the question is: Why have a 32-bit package on my system if the the 64-bit package does everything the 32-bit does? For packages like Firefox where some plugins require a 32-bit Firefox, it's obvious why I would want a 32-bit version of Firefox on my system. But, for most other packages, what's the point? What is a 32-bit version of Evolution going to do that the 64-bit one won't? Why waste my hard drive space with that--and then waste bandwidth on updating both versions of the program? It seems that the only 32-bit packages I should need are those which require/depend on programs/drivers for which there are no 64-bit alternatives. (BTW: I don't think 32-bit and 64-bit packages are mixed in the same repos; I'm pretty sure each get their own, right?) |
You're saying you have redundant packages installed on the same computer? I'm relatively sure that that's a bad idea, and ought to be fixed.
|
Yep, there are plenty of redundant packages, and this is on a fresh install.
So, how much of that is normal? |
Well, someone more experienced than I should chime in, but I generally believe that if you have two architectures of the same package on your system, something unintended has happened, and those packages may conflict. Can you give me the command you used to find this out?
|
That's it. I'm leaving Fedora forever. FC5 had a chance but since then it's just becoming uberbloated shit.
Whatta waste of time. |
I wouldn't call it a waste of time, I rather like it. Maybe it's not for you, but it has its merits.
|
For somethings you need both the 32bit and 64bit package installed. Example, you want to run a 64bit Xorg so you have all the x86_64 Xorg packages installed _but_ you also want to play Enemy Territory. ET is a 32bit-only game so for it to run, it needs 32bit glibc, ALSA/OSS, all Xorg packages it uses (which would be a few).
Right there is probably 100MB of 32bit packages for a single game, the Fedora distro is aimed at newbies who never have to worry about stuff like this so they would by default install a lot of redundant packages just to cover the possibly clueless end user so everything they could possibly install works. If this isn't your cup of tea then borgware is right, find a new distro. There are plenty out there that are strictly 64bit that would probably suit your needs. |
Quote:
|
All times are GMT -5. The time now is 05:07 AM. |