Re: [arch-general] [arch-dev-public] Multilib on Archlinux x86_64
Thomas Bächler wrote:
Andreas Radke schrieb:
It's more a question what Arch64 was founded for: to be the bleading edge leading _pure_ 64bit distro around. That's been its goal since the project has started. And I think we did a good job.
You may have missed the early discussions when we made decisions that we don't want (though we have could have) multilib compatibility and bi-arch gcc. That was a strict law. It was our way to push the efforts to once get it the same level where the x86 world is.
I missed the discussions, maybe. But this is not a discussion we had a few years ago, this is the discussion we are having now. And just saying "A few years ago, we wanted it this way" is not a good reason.
Offering 32bit compat stuff always means to make it easy for users
No, not to make it easy, but make it possible. As I said in my reply to Daniel, I need a 64 bit OS, but I also need mixed 32/64 bit environments.
but takes much pressure from companies and opensource developers give the x86_64 architecture the time and responsibility it is worth. You can compare it to the question to support closed source stuff or not. We made our decision long ago. So please respect it.
We never denied closed source software out of principle. We always made things "just work". I want standard applications to "just work", without having to bother about which architecture I am on.
Now, again, you gave me a list of ideological reasons not to do it, but where exactly is the point where this damages your "pure" system technically?
It's about the technical purity. It's this that makes us different from the other distro's. Otherwise we're just on the road to the next ubuntu. And if you really want 32 bit stuff running on x86-64, just use a 32 bit chroot and don't bother with the multilib stuff. Glenn
On Tue 2008-07-08 23:38, RedShift wrote:
Thomas Bächler wrote: [...]
Now, again, you gave me a list of ideological reasons not to do it, but where exactly is the point where this damages your "pure" system technically?
It's about the technical purity. It's this that makes us different from the other distro's. Otherwise we're just on the road to the next ubuntu. And if you really want 32 bit stuff running on x86-64, just use a 32 bit chroot and don't bother with the multilib stuff.
Well, I see a lot of lib32-* packages in the [community] repo, this means people do want this stuff; at the same time, lib32 packages kind of suck (just read a PKGBUILD to find out why). Arch always provided closed-source software too, so there is no such "purity" to maintain. Thomas proposed to create an ad-hoc repo, so the *-32bit won't even pollute the official repos, I don't see how cleaner this could be; If you don't enable it, then it won't affect your system at all. P.s. There should be a Godwin's-like Law for the phrase "we are on the road to Ubuntu"... -- Alessio (molok) Bolognino Please send personal email to themolok@gmail.com Public Key http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xFE0270FB GPG Key ID = 1024D / FE0270FB 2007-04-11 Key Fingerprint = 9AF8 9011 F271 450D 59CF 2D7D 96C9 8F2A FE02 70FB
It's about the technical purity. It's this that makes us different from the other distro's. Otherwise we're just on the road to the next ubuntu. And if you really want 32 bit stuff running on x86-64, just use a 32 bit chroot and don't bother with the multilib stuff.
It's not at all about technical purity. This makes no changes to Arch 64, it's separate. Arch64 remains pure. Technically, it's better than the existing lib32 efforts too. Let's be realistic here. A computer is a tool to be used. Not that great a tool if it doesnt do what you need it to. Some people need flash and other closed source things. +1
James Rayner wrote:
It's about the technical purity. It's this that makes us different from the other distro's. Otherwise we're just on the road to the next ubuntu. And if you really want 32 bit stuff running on x86-64, just use a 32 bit chroot and don't bother with the multilib stuff.
It's not at all about technical purity. This makes no changes to Arch 64, it's separate. Arch64 remains pure.
Technically, it's better than the existing lib32 efforts too.
Let's be realistic here. A computer is a tool to be used. Not that great a tool if it doesnt do what you need it to. Some people need flash and other closed source things.
+1
Im with James here and i can help test things if needed. +1 -- Douglas Soares de Andrade -- ThreePointsWeb - www.threepointsweb.com -- Python, Zope e Plone == Archlinux Trusted User - dsa ** Quote: Old programmers never die; they exit to a higher shell.
participants (4)
-
Alessio Bolognino
-
Douglas Soares de Andrade
-
James Rayner
-
RedShift