it's a iso.bz2 because I can create it with mk9660 by using
the same proto, the other option was writing a small program
that used proto(2) to list the files and then create the tar.
mk9660 was already there so...
it didn't look like a pain, because you can mount an iso almost
everywhere now a day
Why .iso.bz2?
Wasn't .tgz enough?
Just wondering.
On Thu, Dec 10, 2009 at 6:25 PM, Federico G. Benavento
wrote:
> hola,
>
> we've been thinking about making contrib faster for some time
> now and we finally got something significantly speed improvemnets.
>
> It still uses replica but instead of
hola,
we've been thinking about making contrib faster for some time
now and we finally got something significantly speed improvemnets.
It still uses replica but instead of pulling from sources, it grabs a
.iso.bz2 for the package, mounts it and pulls from there (locally), the
old behaviour is sti
