FS#40307 - [pigz] Package should "provide" gzip

Attached to Project: Community Packages
Opened by Dennis (dennis123123) - Sunday, 11 May 2014, 14:32 GMT
Last edited by Jonathan Steel (jsteel) - Sunday, 18 May 2014, 21:39 GMT
Task Type Feature Request
Category Packages
Status Closed
Assigned To Jonathan Steel (jsteel)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

It would be useful if this package provided gzip (as a symlink to pigz of course),
so that all software would use this faster implementation if installed.
This task depends upon

Closed by  Jonathan Steel (jsteel)
Sunday, 18 May 2014, 21:39 GMT
Reason for closing:  Won't implement
Comment by Jonathan Steel (jsteel) - Sunday, 11 May 2014, 20:44 GMT
If I understand you correctly, that would mean having this conflict with gzip; a core/base package. People installing clonezilla would have to remove gzip.

I think the best thing is to build this yourself via the ABS with your proposed changes, or remove the gzip binary and create a symlink.
Comment by Dennis (dennis123123) - Sunday, 11 May 2014, 20:56 GMT
Yes, this could replace gzip. It is a drop-in replacement so there wouldn't be any other changes needed to other packages.
Comment by Jonathan Steel (jsteel) - Sunday, 11 May 2014, 21:33 GMT
What about the other binaries gzip provides? Pigz doesn't provide (all) these as far as I know.

gzip /usr/bin/gzexe
gzip /usr/bin/uncompress
gzip /usr/bin/zcat
gzip /usr/bin/zcmp
gzip /usr/bin/zdiff
gzip /usr/bin/zegrep
gzip /usr/bin/zfgrep
gzip /usr/bin/zforce
gzip /usr/bin/zgrep
gzip /usr/bin/zless
gzip /usr/bin/zmore
gzip /usr/bin/znew

Also I see no evidence upstream intend the use of pigz through the gzip command, and we follow upstream. Probably other software should be changed (upstream) to use pigz if available. In the meantime I still think it would be best to manage this yourself.

Loading...