From: Marius Mauch <genone@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] December 15th Meeting Summary
Date: Mon, 19 Dec 2005 20:29:43 +0100 [thread overview]
Message-ID: <20051219202943.6c8693f9@sven.genone.homeip.net> (raw)
In-Reply-To: <1135017904.11584.70.camel@onyx>
[-- Attachment #1: Type: text/plain, Size: 1193 bytes --]
On Mon, 19 Dec 2005 13:45:04 -0500
solar <solar@gentoo.org> wrote:
> If you do that please set it as a blocker for the .54 release.
> Reintroducing ChangeLog/metadata.xml to Manifests would be a undesired
> regression. Nothing in the portage as of <=.53 make direct use of
> those two files and there is no security value in bloating the digest
> format with them. Thats why they were removed 2.0.51.21
>
> Making the argument for maybe portage in the future will use them is
> not valid as they are currently omited and we/I have been told before
> by the portage team (ferringb & jstubbs iirc??) that portage itself
> wont be doing any .xml parsing in it's core. IE So that means not
> today nor tomorrow will anything need to depend on those files in
> order to build.
Name a single portage version that does *not generate* manifest entries
for them (hint: there is none). They are only ignored right now during
verification. So it's in no way a regression.
Marius
--
Public Key at http://www.genone.de/info/gpg-key.pub
In the beginning, there was nothing. And God said, 'Let there be
Light.' And there was still nothing, but you could see a bit better.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-12-19 19:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-16 3:47 [gentoo-dev] December 15th Meeting Summary Mike Frysinger
2005-12-19 17:37 ` Marius Mauch
2005-12-19 18:07 ` Alec Joseph Warner
2005-12-19 18:37 ` Mike Frysinger
2005-12-19 18:45 ` solar
2005-12-19 19:29 ` Marius Mauch [this message]
2005-12-20 21:21 ` solar
2005-12-20 3:01 ` Brian Harring
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=20051219202943.6c8693f9@sven.genone.homeip.net \
--to=genone@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