[Bug 4876] rename "boot.iso" to a better/full name

[Feth Arezki]

https://bugs.mageia.org/show_bug.cgi?id=4876

--- Comment #23 from Feth Arezki <feth+mageia-***@public.gmane.org> 2012-11-30 10:08:51 CET ---
Disclaimer: I don't have the slightest understanding of the process.
I imagine the following would help provide meaningful bug reports:
* a sequence number to be included in the downloaded iso name (and inside the
iso, in a txt file).
* a way to match this number with package versions.

Perhaps you know of another way to provide the same functionality. Note that a
date is an acceptable sequence number.

[Thomas Backlund]

https://bugs.mageia.org/show_bug.cgi?id=4876

--- Comment #22 from Thomas Backlund <tmb-***@public.gmane.org> 2012-11-30 09:58:52 CET ---

Yep, that's the "moving target" ...

they get rebuilt for every new kernel released, and also for other changes done
to any of the packages used during build and other fixes to the installer boot
process.

And as the stage2 they load (installer or rescue mode) also gets
changed/updated between alpha/beta/rc releases, naming the iso more than
"Cauldron" in development process is not really realistic...

Then you have the fact that packages in Cauldron gets updated too, so the repos
are not staying the same as alpha/beta/rc isos either :)

But we should atleast make the naming more clear, and also include arch for
those that downloads from both arches and forgets wich one is wich :)

[Romain d'Alverny]

https://bugs.mageia.org/show_bug.cgi?id=4876

--- Comment #24 from Romain d'Alverny <rdalverny-***@public.gmane.org> 2012-11-30 10:18:47 CET ---
It's not that the Web page logic is flawed, it's that it's different than from
the way the boot.iso is generated/updated today, because it takes a different
view to the issue of downloading Mageia:

the Web page is to provide download links to final, static images (of each
build/release):
they are not expected to change

But, in the case of providing netinstall images too on this page, only boot.iso
was available, with an identical filename in different locations:

- yes, it's a moving target for Cauldron, but that's a temporary downside -
in that, yes, as Thomas suggested, it would be beneficial to have a freezed
copy of boot.iso and so on each Cauldron release - as it will be beneficial
later to have freezed pre-installed VM images along the other ISO images).
Correct me if I'm wrong, but it's not an issue on final releases (1, 2 to this
day) as the files tree doesn't change anymore (but for updates)?

- that's in part the reason why the advertized download size doesn't always
match the actual download size; but download size is purely indicative anyway;

- that's in part the reason we don't have checksums for these ISOs either;

- yes, the downloaded file name doesn't match the advertised name on the Web
page, but that's linked to the above again. If we could have a freezed copy
under such an explicit name under iso/, that would be perfect.

- no, the Web site will not provide the download client with a specific
Content-Name, because:
- downloads are actually dispatched to files hosted on (http, ftp) mirrors,
all over the world;
- rewriting on the fly the downloaded file name to the client means to
control each mirror;
- a temporary, imperfect solution could be to symlink from iso/ to actual
files, but that won't fix the point that the linked boot.iso change over time;
- making a freezed, appropriately named copy of the boot.iso on each
release would fix that.