From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Proposal: patches.gentoo.org
Date: Tue, 12 Oct 2004 16:17:03 -0400 [thread overview]
Message-ID: <1097612223.22838.4.camel@localhost> (raw)
In-Reply-To: <416C370C.1070702@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1165 bytes --]
On Tue, 2004-10-12 at 15:57 -0400, Nick Dimiduk wrote:
> Chris Gianelloni wrote:
>
> > 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.
> >
>
> Why do we need a separate location for patches? How are they
> fundamentally different from the sources in distfiles?
Write a patch yourself and add it to /space/disfiles-local and see how
long it takes to get to *all* the mirrors. Now look at how many bugs
you have for missing files (your patch).
The point is that people want to see the patches removed from
${FILESDIR} and moved to ${DISTDIR}, but the distfiles replication is
too slow for this to work properly. Because of this, we came up with
this proposal for a temporary location to hold patches that are
available on-demand and immediately, before the distfiles sync takes
place.
Currently, many of us are using dev.gentoo.org for this purpose. This
proposal is to move this to a supported infrastructure with some
redundancy rather than a single point of failure.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-10-12 20:17 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
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 [this message]
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=1097612223.22838.4.camel@localhost \
--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