Mailinglist Archive: opensuse-factory (1176 mails)
| < Previous | Next > |
Re: [opensuse-factory] RFC: Replacing default gzip and bzip2 command line tools
- From: Ralf Lang <lang@xxxxxxxxxxxxx>
- Date: Mon, 5 Sep 2011 10:19:31 +0200
- Message-id: <201109051019.31812.lang@b1-systems.de>
Am Sonntag, 4. September 2011, 17:30:11 schrieb Per Jessen:
Ok, then I missunderstood you a bit. Thank you for clarifying.
In the sense of 'it has been working before' you are certainly right. In the
sense of 'this is the right way for now and later', I am not so certain. This
is, if interfaces are in fact compatible (there was some dispute on this). If
the process accepts the gzip input parameters and spits out gzip files, I see
no need to guarantee which 'gzipper' sits in between.
The arguments for using gzip at all in automated tasks are fast results and
backwards compatibility - as opposed to best feasible compression. Speed could
be improved by pigz, compatibility of the resulting archives is not broken.
--
Ralf Lang
Linux Consultant / Developer
B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
Ralf Lang wrote:
Am Sonntag, 4. September 2011, 15:51:28 schrieb Per Jessen:
Philipp Thomas wrote:
On Sun, 4 Sep 2011 00:51:09 +0200, Rüdiger Meier <sweet_f_a@xxxxxx>
wrote:
To say it again I like pigz. But renaming ... ?Then 99% of all users will continue to use gzip just because they
Why not replacing it in /usr/bin/compress - the Posix way to define
a Z compressor. If user asks for gzip please give him gzip.
don't know better.
Which isn't really a problem, is it?
If it wasn't viewed as the wrong thing, the question had not been
raised.
Thank you, I am aware of that. I was trying to argue that that view is
wrong.
Ok, then I missunderstood you a bit. Thank you for clarifying.
In the sense of 'it has been working before' you are certainly right. In the
sense of 'this is the right way for now and later', I am not so certain. This
is, if interfaces are in fact compatible (there was some dispute on this). If
the process accepts the gzip input parameters and spits out gzip files, I see
no need to guarantee which 'gzipper' sits in between.
The arguments for using gzip at all in automated tasks are fast results and
backwards compatibility - as opposed to best feasible compression. Speed could
be improved by pigz, compatibility of the resulting archives is not broken.
--
Ralf Lang
Linux Consultant / Developer
B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
| < Previous | Next > |