public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Robin H. Johnson" <robbat2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] GLEP59 - Manifest2 hashes
Date: Thu, 4 Feb 2010 02:57:05 +0000	[thread overview]
Message-ID: <robbat2-20100204T024714-596935539Z@orbis-terrarum.net> (raw)
In-Reply-To: <7c612fc61002012206n59c89f90rd3a0e780321a4c59@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2248 bytes --]

On Mon, Feb 01, 2010 at 11:06:15PM -0700, Denis Dupeyron wrote:
> Agreed. I would suggest to use this series of GLEPs as examples of
> what to do for future GLEP writers.
I've actual considered breaking them up even further.

> replace
> "We should be prepared to add stronger checksums wherever possible,
> and to remove those that have been defeated."
> with:
> "Stronger checksums shall be added as soon as an implementation is
> available in Portage. Weak checksums may be removed as long as the
> depreciation process is followed (see below)."
+1 on that wording, I'll commit when I am next able to. Do see already
how I partially adapted for Cardoe's requests.

> And then, in "Checksum depreciation timing" I would prefer that the
> description of what needs to be done in the present situation was used
> as an example after a more general rule is stated. Something like:
I'd propose the following variant:
=====
A minimum set of depreciated checksums shall be maintained only to
support old package manager versions where needed by historically used
trees: 
- New package manager versions should NOT use depreciated checksums in
  Manifests when newer checksums are available.
- New trees with that have never used the depreciated checksums may omit
  them for reasons of size, but are still strongly suggested to include
  them.
- Removal of depreciated checksums shall happen after no less than 18
  months or one major Portage version cycle, whichever is greater.
=====

I'm not editing these into the checksum GLEP right now, as I'm sitting
in the food court at the airport, with my flight boarding shortly.
Most probably will be committed from my hotel room tomorrow night in
Brussels.

Signing off now, from an airport with bizarre wireless:
More than 45% of connections fail to start, but when they do, they're
good for more than 20Mbit. That's after you deal with the their broken
DNS in the auth mechanism (I'm probably the only person with working
wireless right now, so it's all the bandwidth to myself).

-- 
Robin Hugh Johnson
Gentoo Linux: Developer, Trustee & Infrastructure Lead
E-Mail     : robbat2@gentoo.org
GnuPG FP   : 11AC BA4F 4778 E3F6 E4ED  F38E B27B 944E 3488 4E85

[-- Attachment #2: Type: application/pgp-signature, Size: 330 bytes --]

  reply	other threads:[~2010-02-04  2:58 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
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 [this message]
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=robbat2-20100204T024714-596935539Z@orbis-terrarum.net \
    --to=robbat2@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