public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Thomas Sachau <tommy@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Next council meeting on 7 Dec 2009 at 1900UTC
Date: Mon, 30 Nov 2009 18:57:25 +0100	[thread overview]
Message-ID: <4B140785.1070006@gentoo.org> (raw)
In-Reply-To: <7c612fc60911251350k3560b7d7sf4e9c867a30b0d90@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1861 bytes --]

Denis Dupeyron schrieb:
> The next council meeting will be on 7 Dec 2009 at 1900UTC. If you want
> us to discuss things please let us know in reply to this email. What
> is already known is we'll talk about mtime preservation and prefix.
> You can find threads about those at:
> http://archives.gentoo.org/gentoo-dev/msg_a9e26414f2278275bdfa08baf839704f.xml
> http://archives.gentoo.org/gentoo-dev/msg_2a62689c71f95e4de5699a330b8b5524.xml
> 
> Denis.
> 
> 

Hm, i requested the discussion of real multilib support for portage 2 months ago, i requested it for
the following council meeting, i requested it for the last council meeting and i requested it for
the next council meeting. I hope, it will finally get a place on 7 Dec 2009.

I have a git branch with a modified 2.2_rc* version of portage with included multilib support. I
already wrote about basic implementation 2 months ago in the conversation on this list with vapier.

Since zmedico wants a council-ok before accepting any patches for multilib-support in portage, i
request this. My main idea behind this request is, that more people will have a look and there are
potentially more people involved in improving it. In addition it allows more people to easily get
required 32bit libs the way they want them (specific version, specified USE flags, self-compiled, so
up-to-date unlike the emul-linux-x86-* packages).

Since the code may change in the future, my idea is to restrict it currently only to 2.2_rc*
versions and in addition a required feature (e.g. FEATURES="multilib"). Once everyone is ok with the
code and the way it works, it could be proposed as an PMS-update. If other PM-mantainers are
interested in improving it before, they are of course free to also help improving the code and the
way it works.


-- 
Thomas Sachau

Gentoo Linux Developer


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 316 bytes --]

      parent reply	other threads:[~2009-11-30 17:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-25 21:50 [gentoo-dev] Next council meeting on 7 Dec 2009 at 1900UTC Denis Dupeyron
2009-11-26  1:34 ` Brian Harring
2009-11-26  1:39   ` Zac Medico
2009-11-26 15:31   ` Ciaran McCreesh
2009-11-26 16:33     ` Brian Harring
2009-11-26 16:46       ` Ciaran McCreesh
2009-11-27  8:08         ` Brian Harring
2009-11-30 11:30 ` Antoni Grzymala
2009-11-30 11:41   ` Antoni Grzymala
2009-11-30 21:18   ` [gentoo-dev] GPG Infrastructure for Gentoo (Was Council Meeting) Richard Freeman
2009-11-30 22:28     ` Dawid Węgliński
2009-12-01  1:27     ` Robin H. Johnson
2009-12-03 10:32       ` [gentoo-dev] Individual developer signing Torsten Veller
2009-12-03 12:51         ` Thilo Bangert
2009-12-03 20:35         ` Robin H. Johnson
2009-12-11 16:32           ` [gentoo-dev] " Torsten Veller
2009-12-01  1:08   ` [gentoo-dev] Tree Integrity GLEPS for final review and council approval Robin H. Johnson
2009-11-30 17:57 ` Thomas Sachau [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=4B140785.1070006@gentoo.org \
    --to=tommy@gentoo.org \
    --cc=gentoo-dev@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