>
> There should be one zcat and it should always be gzip. This won't
> break anything as gzip understands .Z files...
>
> Making zcat point to compress even sometimes will definitely break
> things; IME much of the Linux world has been assuming it's gzip for a
> number of years. That se
Yves Arrouye writes:
>Michael Meskes writes:
> > Package: compress-package
> > Version: 1.2-1
> >
> > Compiling and installing the compress source found on ftp.inria.fr
> > I get a file /usr/bin/zcat. However, gzip already install zcat in
> > /bin. I cannot see how it's useful to have both. :-)
>
Yves Arrouye writes:
> Hmmm. This is somewhat more complex than it looks like. I cannot just
> remove /usr/bin/zcat because it is intimately linked with compress.
> If you say 'man compress' for example you'll get the synopsis for zcat
> too and if the corresponding zcat would not be provided then
> Hmmm. This is somewhat more complex than it looks like. I cannot just
> remove /usr/bin/zcat because it is intimately linked with compress.
I disagree. The job of a package maintainer includes the process of doing
things like this to a package. I have to do the same thing for the tar
package,
Michael Meskes writes:
> Package: compress-package
> Version: 1.2-1
>
> Compiling and installing the compress source found on ftp.inria.fr I get a
> file /usr/bin/zcat. However, gzip already install zcat in /bin. I cannot see
> how it's useful to have both. :-)
Hmmm. This is somewhat more c
Package: compress-package
Version: 1.2-1
Compiling and installing the compress source found on ftp.inria.fr I get a
file /usr/bin/zcat. However, gzip already install zcat in /bin. I cannot see
how it's useful to have both. :-)
Michael
--
Michael Meskes |_ __ _
6 matches
Mail list logo