From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5875 invoked from network); 12 Oct 2004 23:20:11 +0000 Received: from smtp.gentoo.org (156.56.111.197) by lists.gentoo.org with AES256-SHA encrypted SMTP; 12 Oct 2004 23:20:11 +0000 Received: from lists.gentoo.org ([156.56.111.196] helo=parrot.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.41) id 1CHVwB-0004SF-3n for arch-gentoo-dev@lists.gentoo.org; Tue, 12 Oct 2004 23:20:11 +0000 Received: (qmail 11911 invoked by uid 89); 12 Oct 2004 23:20:10 +0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 15112 invoked from network); 12 Oct 2004 23:20:10 +0000 From: Chris Gianelloni Reply-To: wolf31o2@gentoo.org To: gentoo-dev@lists.gentoo.org In-Reply-To: <1097614639.24858.11.camel@sixthstreet.formanonline.com> References: <1097608185.20261.8.camel@cgianelloni.nuvox.net> <20041012212759.459bb1fe@andy.genone.homeip.net> <20041012201024.GA11999@twobit.net> <1097614639.24858.11.camel@sixthstreet.formanonline.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-v1J4aubbC6c5OABtljN9" Organization: Gentoo Linux Date: Tue, 12 Oct 2004 19:20:43 -0400 Message-Id: <1097623243.3073.4.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.0.0 Subject: Re: [gentoo-dev] Proposal: patches.gentoo.org X-Archives-Salt: 2970dc51-c584-4e88-bb4b-e775b7ffb244 X-Archives-Hash: 02f1f219b4c4fcb69af64f56dc5875a0 --=-v1J4aubbC6c5OABtljN9 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Tue, 2004-10-12 at 16:57 -0400, Jeffrey Forman wrote: > (1) A single point of distribution is just a bad idea imho. Imagine a > critical patch that MUST GET OUT IMMEDIATELY (differing opinions of > 'must get out now' apply). You get thousands, even tens of thousands of > people hitting patches.g.o and you can wave goodbye to that machine. Except for the idea would be to use a few machines as "patches.gentoo.org" not a single machine. I think you missed that point in my posting. > (2) The distribution network is there for a reason. Let me be the first > one to admit that it isnt perfect. Once you place something on > /space/distfiles-local, it hits two machines before it hits the world, > taking between an hour and four hours (theoretically) to go public. > Latency is involved in whichever solution we can propose, short of > giving everyone write access to our master mirror. Remember that we're talking patch files and only as a temporary store until the files hit the main mirror infrastructure. > (3) Whether we use distfiles mirrors, or the rsync rotation to > distribute patches, this has not been decided upon. The idea was > broached for a couple minutes earlier today but not even a preliminary > solution was conjured. Actually, we had a decent idea, which Kurt then asked someone to write up, so I did. The idea would be to use the rsync servers, which was the reason I originally put information about something like /space/patches- local as we do *not* want it to mirror distfiles, only the critical patches that we say *have to get out quickly* and we don't want to wait for the normal distfiles mirroring to take place. Anything other than this pretty much makes the whole system useless and adds a *ton* over extra overhead that we were never discussing. > Infra has complete control over the rsync.g.o rotation, so coming up > with ways to improve it that way can be worked out. I am sure this will > be a topic during the next dev meeting, if not listed, I will definitely > mention it. That's what this was supposed to be... ;] > On Tue, 2004-10-12 at 16:10, Nicholas Jones wrote: > > And rewritten for clarity: > >=20 > > 1. developer creates an ebuild which needs a patch > > 2. SRC_URI=3D"mirror://gentoo/patchname http://patches.gentoo.org/patch= name" > > 3. Uploads files to dev.gentoo.org:/space/distfiles-local > > 4. developer commits ebuild(s) to cvs > >=20 > > Infra notes: > >=20 > > 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. > >=20 > > 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. > >=20 > > 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). > >=20 --=20 Chris Gianelloni Release Engineering - Operational/QA Manager Games - Developer Gentoo Linux --=-v1J4aubbC6c5OABtljN9 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQBBbGbJkT4lNIS36YERAorQAJ97RyH79JtUkKvwESCc93ZK34TKuwCggGpg HT45aBC/AH4flpK14RwSNhc= =Ae9A -----END PGP SIGNATURE----- --=-v1J4aubbC6c5OABtljN9--