public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Thomas Rösner" <Thomas.Roesner@digital-trauma.de>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] real multilib support
Date: Tue, 27 Mar 2007 11:05:49 +0200	[thread overview]
Message-ID: <4608DE6D.5030208@digital-trauma.de> (raw)
In-Reply-To: <20070322230742.2fedab84@c1358217.kevquinn.com>

Hi,

Kevin F. Quinn schrieb:
> On Thu, 22 Mar 2007 15:37:52 +0000
> Simon Cooper <thecoop@runbox.com> wrote:
>
>   
>> Whats the status of real, proper, compiled multilib support? Is it
>> 'being worked on'?
>>     
>
> You might be interested in:
>
> http://dev.gentoo.org/~kanaka/auto-multilib/
>
> which doesn't need ABI dependencies - ABI dependencies and
> associated tracking could turn out to be a bit of a nightmare in
> practice.  Kanaka explains some of the reasons why.
>   

The doc there doesn't get me too excited, however. I don't want to drag 
a 32bit userland around for /every/ ebuild that has multilib support. 
Perhaps this is more useful if combined with useflag dependencies (which 
are about to come in portage and are in paludis) - that way you'd never 
bother to set one of the ABI useflags, but ebuilds could depend on 32bit 
versions of libraries. Things like installing gtk+ themes for the 32bit 
gtk libs, too, would be the only thing you'd have to specify manually 
that way.

>> Whats the main things holding it back at the moment?
>>     
>
> My guess would be that there's no desperate need for it.  The existing
> workarounds; i.e. chroots, emul packages etc work well enough for the
> amd64/x86 pair anyway.
>   

They "sort of" work, yes. But currently Gentoo isn't using the amd64-x86 
compatibility to it's full potential. You'd think it's easier for a 
source based distro to do this, but right now changes to portage are 
harder than they should be (I agree with ciaranm on this one without 
even looking to hard at the portage code, the time features spend in the 
queue just speaks for itself). This is an area where portage 
alternatives really could shine, funnily I don't see them picking this 
up at all.

Well, at least the current state of multilib keeps me from installing to 
much non-free software. I collect some GNU/karma points that way ;-).

Regards,
    Thomas


-- 
gentoo-amd64@gentoo.org mailing list



      reply	other threads:[~2007-03-27  9:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-22 15:37 [gentoo-amd64] real multilib support Simon Cooper
2007-03-22 18:02 ` Olivier Crête
2007-03-27  5:32   ` [gentoo-amd64] " Duncan
2007-03-27  9:08     ` Thomas Rösner
2007-03-27 12:53       ` Kevin F. Quinn
2007-03-28  2:04         ` Duncan
2007-03-28 21:24           ` Thomas Rösner
2007-03-28 22:14             ` Kevin F. Quinn
2007-03-28 23:49             ` Duncan
2007-03-22 19:35 ` [gentoo-amd64] " Thomas Rösner
2007-03-22 21:30   ` Boyd Stephen Smith Jr.
2007-03-22 22:07 ` Kevin F. Quinn
2007-03-27  9:05   ` Thomas Rösner [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4608DE6D.5030208@digital-trauma.de \
    --to=thomas.roesner@digital-trauma.de \
    --cc=gentoo-amd64@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox