public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: solar <solar@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] December 15th Meeting Summary
Date: Tue, 20 Dec 2005 16:21:10 -0500	[thread overview]
Message-ID: <1135113670.10361.128.camel@onyx> (raw)
In-Reply-To: <20051219202943.6c8693f9@sven.genone.homeip.net>

On Mon, 2005-12-19 at 20:29 +0100, Marius Mauch wrote:
> 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
...


> 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.

sigh I just checked and you are correct it does still create them, so
I'll happily recant on the word regression. It however seems pointless
to include them in creation. Currently the 2 unused lines are taking up
about ~1.1M in the tree, when we have several additional hashes I can
only imagine that it would use significantly more space than currently.

-- 
solar <solar@gentoo.org>
Gentoo Linux

-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2005-12-20 21:24 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
2005-12-20 21:21       ` solar [this message]
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=1135113670.10361.128.camel@onyx \
    --to=solar@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