From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Proposal: patches.gentoo.org
Date: Tue, 12 Oct 2004 15:09:45 -0400 [thread overview]
Message-ID: <1097608185.20261.8.camel@cgianelloni.nuvox.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 2091 bytes --]
We were talking about this on IRC due to the growing concern over
patches and other files in ${FILESDIR} in the portage tree. This is
basically the idea that we came up with to resolve the problem.
The proposal is to get infrastructure to provide a temporary location
for developers to upload patches which are necessary to be immediately
available to users. This space would be writable by all CVS developers
and would be accessible to the world via http. Developers would use
this space for temporary storage only for patches which are
created/rolled in-house.
For the sake of simplicity, I am going to call this server (though it
could be any number of servers) patches.gentoo.org for the remainder of
this document.
Ramereth suggesting using the existing rsync.gentoo.org infrastructure
servers for this task. This would simplify replication, since the
replication could be done via rsync and use the same schedule as the
master portage tree replication. This would ensure that the patches are
available at the same time as the ebuild.
The developer would use this temporary location as follows:
1. developer creates an ebuild which needs a patch
2. developer puts SRC_URI="patches.gentoo.org/${P}-$patchname" in the
ebuild, at the end of the SRC_URI definition
3. developer uploads patch to dev.gentoo.org:/space/patches-local and
dev.gentoo.org:/space/distfiles-local
4. developer commits ebuild(s) to cvs
The patch would replicate to the rsync boxes and would be available via
http immediately.
Remember that portage tries the Gentoo mirrors in ${GENTOO_MIRRORS}
before checking SRC_URI, so once the files hit the community mirrors,
the temporary location in SRC_URI would no longer be used.
A cron job would be added to the machine to clean out files older than 7
days. This gives the mirrors plenty of time to locally mirror the
patches. This also reduces the amount of space required on the machine
(s) hosting the files.
--
Chris Gianelloni
Release Engineering - Operations/QA Manager
Games - Developer
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2004-10-12 19:12 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-12 19:09 Chris Gianelloni [this message]
2004-10-12 19:12 ` [gentoo-dev] Proposal: patches.gentoo.org 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
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=1097608185.20261.8.camel@cgianelloni.nuvox.net \
--to=wolf31o2@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