From: Martin Schlemmer <azarah@gentoo.org>
To: Gentoo-Dev <gentoo-dev@robin.gentoo.org>
Subject: Re: [gentoo-dev] Large files still in files/
Date: Tue, 08 Mar 2005 09:39:56 +0200 [thread overview]
Message-ID: <1110267596.8842.141.camel@nosferatu.lan> (raw)
In-Reply-To: <422CA2FF.80803@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1947 bytes --]
On Mon, 2005-03-07 at 12:52 -0600, Lance Albertson wrote:
> Chris Gianelloni wrote:
> > On Mon, 2005-03-07 at 18:57 +0200, Martin Schlemmer wrote:
> >
> >>>I kind of like this idea, however, I think it's idealistic. Patches need
> >>>to be modified very frequently. Especially when we combine multiple
> >>>patches and make them all work with USE flags.
> >>>
> >>>A great deal of our patches really are written specifically work with our
> >>>ebuilds.
> >>>
> >>>What is the real percentage of space usage from compressed or uncompressed
> >>>patches? How big of a problem is it?
> >>>
> >>
> >>Also the problem is that especially if you have a rapid changing
> >>package, where the patches changes a lot, putting it in distfiles is a
> >>pita, as you have to scp it, then wait an hour to 3 depending on how
> >>lucky you are, and then only commit. And especially if you forgetful
> >>like me, you tend to forget to either come back and commit the new
> >>version/revision, or to copy the new tarball to distfiles ...
> >
> >
> > This was why we were asking for a "packages.gentoo.org" that could
> > either be a single or multiple machines. It could even replace
> > the /space/distfiles-local, as everything from it could be pushed out to
> > be synched to distfiles. This would make them immediately available,
> > and would alleviate the problem. Once the main distfiles mirrors got
> > the files, they could be deleted from packages.gentoo.org
>
> You mean patches.gentoo.org. Yes, ideally this is something we need to setup. I
> recall having this topic a few months back, but I forgot where it left off.
> Right now dev.g.o is a single point of failure. If it dies, everything you host
> there dies.
>
Well, missed this - I am all for it when some infra monkey gets the
time :)
--
Martin Schlemmer
Gentoo Linux Developer, Desktop/System Team Developer
Cape Town, South Africa
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-03-08 7:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-06 4:19 [gentoo-dev] Large files still in files/ Michael Sterrett -Mr. Bones.-
2005-03-06 5:09 ` Robin H. Johnson
2005-03-08 10:15 ` Michele Noberasco
2005-03-08 13:26 ` Michele Noberasco
2005-03-06 5:27 ` Mark Loeser
[not found] ` <20050206.052901.4667@leftmind.net>
2005-03-06 18:10 ` Anthony de Boer
2005-03-06 20:25 ` Cory Visi
2005-03-07 16:57 ` Martin Schlemmer
2005-03-07 17:38 ` Malte S. Stretz
2005-03-07 17:54 ` Aron Griffis
2005-03-07 18:05 ` Ciaran McCreesh
2005-03-07 18:59 ` Chris Gianelloni
2005-03-07 18:52 ` Chris Gianelloni
2005-03-07 18:52 ` Lance Albertson
2005-03-07 19:15 ` Chris Gianelloni
2005-03-08 7:39 ` Martin Schlemmer [this message]
2005-03-07 15:34 ` 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=1110267596.8842.141.camel@nosferatu.lan \
--to=azarah@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@robin.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