-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 30 Jan 2013 12:30:51 +0100
Michael Weber wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 01/30/2013 10:58 AM, Michał Górny wrote:
> > On Wed, 30 Jan 2013 09:35:12 +0100 Michael Weber
> > wrote:
>
> > We don't want 32-bi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 01/30/2013 10:58 AM, Michał Górny wrote:
> On Wed, 30 Jan 2013 09:35:12 +0100 Michael Weber
> wrote:
> We don't want 32-bit cp. Thomas likes to support every weird idea
> coming from a random user, I don't.
What is wrong with "random" or "user"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 30 Jan 2013 09:35:12 +0100
Michael Weber wrote:
> What's the primary Idea behind multilib at all?
> Isn't it just a workaround to keep prebuild software
> from lazy/incapable/dead upstreams working (skype, ...)?
Yes. And 32-bit wine for 32
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 01/30/2013 09:35 AM, Michael Weber wrote:
> These // can be anything, like different ABIs, different libc
> implementations, different keyword (stable, testing), different
> Distros, - as long as it runs with the current kernel. Well,
> thin-provi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
What's the primary Idea behind multilib at all?
Isn't it just a workaround to keep prebuild software
from lazy/incapable/dead upstreams working (skype, ...)?
Is there any other real use besides bragging about processor
capabilities and compilin
