From: Andrew Cooks <andrew@expertron.co.za>
To: Peter Cech <cech@upc.uniba.sk>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Upcoming repoman check will fail on large files in the tree
Date: Wed, 25 Aug 2004 15:31:35 +0000 [thread overview]
Message-ID: <412CB0D7.4080403@expertron.co.za> (raw)
In-Reply-To: <20040825130836.GC10036@pec.upc.uniba.sk>
Peter Cech wrote:
> None of the files is needed prior to emerge -f. Most of them are never
> used, but have to be transfered on emerge sync and have to be on the
> harddrive. IMO this part of portage tree should be moved out and
> downloaded with sources on fetch step.
I completely agree!
Some of the machines I maintain (like my home machine and my parents')
only have access to 56k dialup and there's no local official rsync
mirror for South Africa. The source files are easy to get hold of and
can easily be transfered by CD/usb device, but keeping the tree in sync
is a much tougher task.
Please keep the tree lean!
Regards
Andrew
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-08-25 13:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-25 13:08 [gentoo-dev] Upcoming repoman check will fail on large files in the tree Peter Cech
2004-08-25 15:31 ` Andrew Cooks [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-29 9:52 Brian Harring
2004-07-29 14:15 ` Mike Frysinger
2004-07-29 19:53 ` Jason Rhinelander
2004-07-30 3:15 ` Georgi Georgiev
2004-07-30 3:20 ` Brian Harring
2004-07-30 3:22 ` Ciaran McCreesh
2004-07-30 4:07 ` Ciaran McCreesh
2004-07-30 7:00 ` Robin H. Johnson
2004-07-30 7:43 ` Ciaran McCreesh
2004-08-25 6:56 ` Tavis Ormandy
2004-08-25 14:40 ` Mike Frysinger
2004-08-25 17:19 ` Robert Moss
2004-08-26 14:34 ` Eldad Zack
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=412CB0D7.4080403@expertron.co.za \
--to=andrew@expertron.co.za \
--cc=cech@upc.uniba.sk \
--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