public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64]  Re: real multilib support
Date: Tue, 27 Mar 2007 05:32:49 +0000 (UTC)	[thread overview]
Message-ID: <pan.2007.03.27.05.32.49@cox.net> (raw)
In-Reply-To: 1174586568.5958.1.camel@localhost

Olivier Crête <tester@gentoo.org> posted
1174586568.5958.1.camel@localhost, excerpted below, on  Thu, 22 Mar 2007
14:02:47 -0400:

> On Thu, 2007-22-03 at 15:37 +0000, Simon Cooper wrote:
>> Whats the status of real, proper, compiled multilib support? Is it
>> 'being worked on'? Whats the main things holding it back at the moment?
> 
> The big missing element is proper portage support. Since it will have to
> maintain parallel dep trees for the difference architectures. And since
> portage is a complicated beast, I don't think any significant work has
> been done in that direction.

FWIW, there had been efforts in that direction, but they had been shelved 
for the time being due to the complexity and difficulty of introducing 
such a major new feature into portage without breaking existing working 
and depended upon code.  The story, even a short version, is long and 
complex and fraught with nasty politics, but ultimately comes to the 
still fresh (last few days) announcement of the first public draft of 
PMS, the package manager spec.  Once package manager API-0 is defined and 
adopted, and the council has made it a priority now so within a few 
months seems reasonable, it'll break a log jam that has been holding up 
all /sorts/ of stuff, including not only major features in portage 
itself, but the development of portage alternatives such as pkgcore and 
paludis as well.  The next 18 months or so could be /very/ interesting, 
as major new Gentoo tree and package manager features like full working 
multilib support that has been frozen for literally years, finally 
becomes possible to practically implement, as this log jam breaks up.

For more info, check the dev list, or look around some of the developer 
blogs.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list



  reply	other threads:[~2007-03-27  5:35 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   ` Duncan [this message]
2007-03-27  9:08     ` [gentoo-amd64] " 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

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=pan.2007.03.27.05.32.49@cox.net \
    --to=1i5t5.duncan@cox.net \
    --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