public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kurt Lieber <klieber@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Proposal: patches.gentoo.org
Date: Wed, 13 Oct 2004 12:43:32 +0000	[thread overview]
Message-ID: <20041013124332.GG26288@mail.lieber.org> (raw)
In-Reply-To: <20041012201024.GA11999@twobit.net>

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

On Tue, Oct 12, 2004 at 04:10:24PM -0400 or thereabouts, Nicholas Jones wrote:
> Immediate availability via the "secondary" host while the primary
> host has yet to receive the files. Once the file is present on the
> primary mirrors it may be deleted from the secondary.

Rather than trying to write a semi-intelligent script that will make a
determination on whether or not a file has made it to the main mirrors
before deleting, I'd much rather just say "all files will exist for N days
and then be deleted".  

If a file doesn't make it to all our mirrors within 24 hours, there's a
larger problem.  Thus, I'd suggest making N = 3 and leaving it at that.

> Ensuring that the patch host is not the primary mirror will be a
> concern, but a script can be devised to ensure duplication of
> the patchname and that a primary mirror is listed prior to it.

This logic should be added to repoman if it's added anywhere.  Also, by
keeping N=3, devs will quickly learn NOT to use this location as a primary
mirror once they start getting deluged with bug reports about SRC_URI being
broken.

> The host for the files should not be accessable for any reason
> except direct filename downloads. No listings (to discourage
> setting it as a mirroring source).

Great idea -- agree 100%.

--kurt

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

  parent reply	other threads:[~2004-10-13 12:43 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-12 19:09 [gentoo-dev] Proposal: patches.gentoo.org Chris Gianelloni
2004-10-12 19:12 ` Ciaran McCreesh
2004-10-12 19:32   ` George Shapovalov
2004-10-12 19:33     ` Ciaran McCreesh
2004-10-13 12:53   ` Kurt Lieber
2004-10-13 13:28     ` Doug Goldstein
2004-10-12 19:27 ` Marius Mauch
2004-10-12 19:52   ` Beber
2004-10-12 20:11     ` Marius Mauch
2004-10-12 20:10   ` Nicholas Jones
2004-10-12 20:50     ` Jeffrey Forman
2004-10-12 20:57     ` Jeffrey Forman
2004-10-12 23:20       ` Chris Gianelloni
2004-10-13 12:43     ` Kurt Lieber [this message]
2004-10-13  9:46   ` Paul de Vrieze
2004-10-13 12:19     ` Lance Albertson
2004-10-13 12:39     ` Kurt Lieber
2004-10-12 19:57 ` Nick Dimiduk
2004-10-12 19:57   ` Ciaran McCreesh
2004-10-12 20:17   ` Chris Gianelloni
2004-10-12 22:04 ` Mike Frysinger
2004-10-13 13:05 ` Kurt Lieber
2004-10-13 15:16   ` Ciaran McCreesh
2004-10-14 12:07     ` Kurt Lieber
2004-10-15 15:13       ` Xavier Neys
2004-10-14 20:38 ` Dylan Carlson
2004-10-14 21:05   ` Mark Loeser
2004-10-15  1:00     ` Chris Gianelloni
2004-10-14 22:08   ` [gentoo-dev] Patch filename conventions (WAS: Proposal: patches.gentoo.org) Dylan Carlson
2004-10-14 22:14     ` Mike Frysinger
2004-10-15  2:20       ` Dylan Carlson
2004-10-15  2:58         ` Donnie Berkholz
2004-10-15  4:24           ` Dylan Carlson
2004-10-15  5:13             ` Donnie Berkholz
2004-10-15  6:01               ` Dylan Carlson
2004-10-15  6:04       ` Robin H. Johnson
2004-10-15 12:16         ` Kurt Lieber
2004-10-15  0:49   ` [gentoo-dev] Proposal: patches.gentoo.org Chris Gianelloni

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=20041013124332.GG26288@mail.lieber.org \
    --to=klieber@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