On Fri, Apr 25, 2008 at 11:27:01AM +0200, Rudolf Kastl wrote:
On Fri, Apr 25, 2008 at 10:47 AM, Jakub Jelinek
<jakub(a)redhat.com> wrote:
> On Fri, Apr 25, 2008 at 05:31:26PM +1000, Rodd Clarkson wrote:
> > On Fri, 2008-04-25 at 08:59 +0200, Hans de Goede wrote:
> > > Hi All,
> > >
> > > I'm planning on updating vegastrike to the new 0.5.0 upstream release
for F-10
> > > and maybe later F-9 / F-8 too, but vegastrike has been dead for a while
and now
> > > makes some huge changes, so better to keep the old trusted version for
F-8 /
> > > F-9 for a while.
> > >
> > > However the 0.5.0 datafiles are 500 Mb b2zipped! So is this a problem?
> >
> > That depends. Are you wanting it installed on the Live CD? 8-]
>
> For Live CD it is obviously out of the question, it wouldn't even fit
> there, but even in the Everything trees 500MB of data for a game is IMHO too
> much. Remember many people mirror the whole Everything tree to do local
> installs etc.
but i really dont see the issue here, simply because you could just
exclude that one package from mirroring. what if someone adds 100 x
5mb packages tomorrow... the everything mirror scripts will then have
to mirror the same size.
yum users will get confused if mirrors start excluding by package name
(instead of by directory). MirrorManager expects that if you have a
directory, you have the _whole_ directory. yum metadata does to. yum
will request the file because the metadata says it's there; the mirror
will return a 404 which the user will see and then move to the next
entry in the mirrorlist; repeat... it'll work, but it'll be ugly.
--
Matt Domsch
Linux Technology Strategist, Dell Office of the CTO
linux.dell.com &
www.dell.com/linux