public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Denis Dupeyron <calchan@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Gentoo Prefix: on EPREFIX, ED and EROOT inside  ebuilds
Date: Wed, 25 Nov 2009 16:43:32 -0700	[thread overview]
Message-ID: <7c612fc60911251543p70dfa240gf09feb46f18e3323@mail.gmail.com> (raw)
In-Reply-To: <20091120090338.GK19586@gentoo.org>

Things seem to be progressing nicely on this front. We have answers to
the questions people had and they look satisfactory to me.

One thing that I think would be valuable is a document that explains
the average dev how to make his/her ebuilds prefix compliant with
links to more details when necessary. I understand that there's the
trivial situations and the less trivial ones. In the latter case it
would be nice to explain why the case isn't trivial and how to fix it.
Using python as an example could be one way to do it. I'm thinking of
something practical that could possibly be patched into devmanual. If
such a document already exists then please just point us to it.

On Fri, Nov 20, 2009 at 2:03 AM, Fabian Groffen <grobian@gentoo.org> wrote:
>> I thought I asked Fabian to work on that at the end of the meeting. In
>> case I didn't then consider this as me officially asking him if he can
>> take care of it. Fabian is this OK with you?
>
> Yes, I agreed coming up with some patch.  I admit I haven't yet even
> looked into it.

Great, thanks. If you can have it ready some time before the meeting
so that all devs can get a chance to review it before the council
members vote on it that will be even better. If you need help don't
hesitate to contact me. I'll try and look for the right people to help
you depending on what you need.

> Technically, Portage trunk already contains the most important bits that
> allow us to continue since yesterday.  The rest is waiting for a formal
> approval of the council, and then it will most probably be me and Zac
> fighting to get the prefix branch merged into trunk.

Good.

> Next to that, it is part of the Prefix team's job to make sure that
> whatever is installed, does not reference the host system when this is
> not absolutely necessary.

Could you give some examples of when it is absolutely necessary?

Denis.



  reply	other threads:[~2009-11-25 23:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-18  9:11 [gentoo-dev] Gentoo Prefix: on EPREFIX, ED and EROOT inside ebuilds Fabian Groffen
2009-10-18 11:57 ` Tomáš Chvátal
2009-10-18 12:31   ` Fabian Groffen
2009-10-19 19:44     ` Fabian Groffen
2009-10-24 19:37       ` Petteri Räty
2009-10-24 20:00         ` Fabian Groffen
2009-11-13 11:43       ` Ulrich Mueller
2009-11-20  8:45         ` Fabian Groffen
2009-11-20  0:26 ` Denis Dupeyron
2009-11-20  1:42   ` Jeremy Olexa
2009-11-20  9:03     ` Fabian Groffen
2009-11-25 23:43       ` Denis Dupeyron [this message]
2009-11-26  8:53         ` Fabian Groffen
2009-11-26 10:01           ` [gentoo-dev] " Duncan
2009-11-26 10:10             ` Fabian Groffen
2009-11-26 10:37               ` Duncan
2009-11-26 10:51                 ` Fabian Groffen
2009-11-26 12:36                   ` Duncan
2009-11-26 15:26                     ` Fabian Groffen
2009-11-26 13:43         ` [gentoo-dev] " Fabian Groffen
2009-11-26  0:01   ` Denis Dupeyron
2009-11-26  9:02     ` Fabian Groffen

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=7c612fc60911251543p70dfa240gf09feb46f18e3323@mail.gmail.com \
    --to=calchan@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