Guillaume,
You have not told us the full story:
1. How did your CTO respond to the need for an addditional first
stage install floppy disk image to support install from an iso file?
2. How did your CTO respond to the need for a constant single name
for the most current beta iso image? This requirement is dictated to
permit incremental download of changes by rsync. Without this
constraint on your operatons, beta-testers will be faced with a
complete near 1 GB download every time the beta iso is changed, which
is totally unnecessary and an enormous load on your server and its
mirrors - rsync downloads only the changes within the server file and
edits them into the local client file.
No version information may be carried in the file name - this is a
general requirement for efficient rsync operation. You have a
VERSION file in the base directory, this is where the detailed
version and timestamp information must be. The iso image can be
mounted on the loop device to access this VERSION file.
Guillaume Cottenceau wrote:
> Yep. New one very soon to be mirrored, our CTO confirmed it to me today.
>
> > > Current cooker has been heavily modified since this third beta, because of
> > > i486, sparc, and alpha port, on which we're currently working.
> >
> > So to test 7.1 I should hunt down beta 3 and not use Cooker then?
>
> Yep, definitely. The cooker by now is "forked" from the future final 7.1
--
Regards,
Ron. [AU] - sent by Mandrake Linux.
