Steve Long wrote:
<snip> .. The one
disadvantage to my design is it needs infra. It needs it's own
repository and rsync.
What does that entail? Would a co-located server suffice?
(If it gets popular, I'd imagine those mirroring current rsyncs etc would
want to mirror the releases as well.)
One of the problems here (IIRC) is that our mirrors are quite full. Not
only must you mirror the release tree (which is trivial in size) you
also have to mirror the distfiles for that tree. Right now our
distfiles are maintained by a wonderful python script that checks the
files in SRC_URI and fetches them to the master when needed; when an
ebuild is removed from CVS, the fetcher will not fetch the file and it
will get removed (after two weeks, afaik).
The bonus is that we then need to have a fetcher that runs over the main
tree and all supported release trees, and this of course increases
mirror size as we now have distfiles in the tree from a year ago to
support a year old release. I am unsure how much space this would take
up; but this is an obstacle that must be overcome (somehow), preferably
by giving infra an estimate on the space reqs.
--
gentoo-dev@gentoo.org mailing list
