From: Denis Dupeyron <calchan@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] GLEP58 - MetaManifest
Date: Mon, 1 Feb 2010 23:27:01 -0700 [thread overview]
Message-ID: <7c612fc61002012227i5a4b2cf5ha08f5a0c87f70ce0@mail.gmail.com> (raw)
In-Reply-To: <robbat2-20100131T094349-748992807Z@orbis-terrarum.net>
You'll find below an email from solar to Robin about MetaManifest. I'm
adding it to this thread (with solar's authorization) as it seems
pertinent.
Denis.
On Thu, Jan 21, 2010 at 6:51 PM, Ned Ludd <solar@gentoo.org> wrote:
> Robin,
>
> I recall you wanted me to mail you what we talked about last nite in
> #gentoo-portage and I'll CC: the council so they have an idea what to
> maybe expect.
>
> So in our talking last night we discussed the fact that if the Manifest
> format has to change why not just get rid of it all together, and save
> some serious in tree space with the new MetaManifest's taking over all
> together. This would include MetaManifest's at the 2-level.
> You said the MetaManifest would need about 4 fields in them to describe
> the distfiles etc. Devs would still push normal Manifest's to the cvs
> tree so DIST can be obtained by the backend infra scripts. But those
> Manifest's could be dropped from the mirroring. if [ -e CVS ] then
> portage would need to use the existing Manifest's
>
> This method would hands down win my vote. As you know I'm not a fan of
> format changes in general as they can make the Gentoo experience suck,
> but if we are going to change formats. Lets do it right.
>
> The only downside I can see in this method is for people like drobbins
> who mirror our tree but overlay right on top of it then provide it back
> out. In such cases we should provide our backend scripts to the public
> so they can re MetaManifest.
>
> I'm probably forgetting all sorts of details from the chat. But
> hopefully this is enough to remind you, as well as giving the other
> council ppl an idea of what to maybe expect.
next prev parent reply other threads:[~2010-02-02 6:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-31 9:20 [gentoo-dev] Tree-signing GLEPs update Robin H. Johnson
2010-01-31 9:48 ` [gentoo-dev] GLEP58 - MetaManifest Robin H. Johnson
2010-02-02 6:27 ` Denis Dupeyron [this message]
2010-02-02 7:35 ` Robin H. Johnson
2010-01-31 9:57 ` [gentoo-dev] GLEP59 - Manifest2 hashes Robin H. Johnson
2010-02-01 5:05 ` Robin H. Johnson
2010-02-01 8:23 ` Doug Goldstein
2010-02-02 6:06 ` Denis Dupeyron
2010-02-04 2:57 ` Robin H. Johnson
2010-02-02 6:09 ` Robin H. Johnson
2010-01-31 10:01 ` [gentoo-dev] GLEP60 - Manifest2 filetypes Robin H. Johnson
2010-01-31 10:04 ` [gentoo-dev] GLEP61 - Manifest2 compression Robin H. Johnson
2010-02-08 1:02 ` Brian Harring
2010-02-08 5:23 ` Robin H. Johnson
2010-02-08 5:50 ` Brian Harring
2010-01-31 10:11 ` [gentoo-dev] Tree-signing GLEPS review notes Robin H. Johnson
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=7c612fc61002012227i5a4b2cf5ha08f5a0c87f70ce0@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