public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jeremy Olexa <darkside@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: gentoo-x86 commit in net-mail/getmail: ChangeLog getmail-4.9.2.ebuild
Date: Fri, 16 Oct 2009 17:23:11 -0500	[thread overview]
Message-ID: <4AD8F24F.2030205@gentoo.org> (raw)
In-Reply-To: <1255680250.4873.5.camel@su.perronet.esiee.net>

Gilles Dartiguelongue wrote:
> Le mardi 13 octobre 2009 à 23:48 +0200, Jeroen Roovers a écrit :
>> On Tue, 13 Oct 2009 21:22:13 +0200
>> Fabian Groffen <grobian@gentoo.org> wrote:
>>
>>> We are working on a proper explanation targetted to devs of this.  I'm
>>> sorry for the inconvenience caused.
>> How large of a change to the tree will this involve? Is it a small
>> number of packages that need to be fixed through the ebuilds right now?
>> will that number grow? Will you notify package maintainers of these
>> changes?
> 
> Apparently not, it's not that the change is complicated but I (and the
> rest of the gnome herd) would rather have an upfront information about
> any kind of changes to our ebuilds than discovering these through
> gentoo-commits...

Jeroen / Gilles : Coming soon. The internal draft was just prepared but 
Fabian will be sending it.

> 
>>> For the moment you can find our own documentation here:
>>> http://www.gentoo.org/proj/en/gentoo-alt/prefix/techdocs.xml
>> Where did you document D -> ED? Can you briefly describe what it does?

See the section "The variables ED and EROOT" on that link. I don't want 
to open it up for discussion on this thread though.

> 
> I'd also like to know why this cannot be handled by the usual D with
> package manager support, this would save a lot of changes to ebuilds
> (like the python abi stuff that still has no documentation afaik).
> 
> I sincerely want to see progress in the way we handle prefix, python
> abis and all the cool stuff that is still in preparation, but let's do
> it in a way to makes every dev aware of it (sending a mail to
> gentoo-dev-announce for example), thanks.

Thanks for your support on behalf of the Prefix team,
-Jeremy




      reply	other threads:[~2009-10-16 22:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1MwzyL-0008Au-Qo@stork.gentoo.org>
2009-10-11 15:14 ` [gentoo-dev] Re: gentoo-x86 commit in net-mail/getmail: ChangeLog getmail-4.9.2.ebuild Torsten Veller
2009-10-13 19:22   ` Fabian Groffen
2009-10-13 21:48     ` Jeroen Roovers
2009-10-16  8:04       ` Gilles Dartiguelongue
2009-10-16 22:23         ` Jeremy Olexa [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=4AD8F24F.2030205@gentoo.org \
    --to=darkside@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