Re: Supporting compression-less release builds

[Greg Troxel <gdt%lexort.com@localhost>]

Martin Husemann <martin%duskware.de@localhost> writes:

>> Note that we sometimes use an explicit compression method elsewhere
>> in the build (eg compressing kernels) that might differ from the
>> compression method for sets.
>
> Indeed, and also some of the compression levels must be high (or used to
> be, maybe the split of DVD images fixed this properly already) to make
> the resulting images fit into certain size restraints.

There is "must be" and there is "if you turn compression down to save
time, then your iso images might be bigger than will fit".   I think the
latter is fine.

> For the original problem, I would do something else: hack the makefiles
> localy to not update the compressed aritfacts at all when some make variable
> is set. If that turns out to be usefull and not totally awful, it could
> even be commited with some warnings in the documentation.

I build releases, rsync them to other machines - often on GbE LAN, and
then update those machines (with scripts in etcmanage).  Yes, the
extensions are baked in, but it might be useful to do this uncompressed,
depending on if gzip beats GbE.

jmmv@'s proposal sounds entirely reasonable to me.