gzipped files in tarball

Bug #408770 reported by Tim Waugh
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
HPLIP
New
Undecided
Unassigned

Bug Description

It's quite bad form to include gzipped files in the actual tarball -- it means that (a) those files are being compressed twice, which gives bad performance for compression compared to having everything compressed together, as it allows common strings to share the global dictionary, and (b) distributions cannot easily apply patches to those files.

Better to ship those files uncompressed in the tarball, just compress the entire tarball.

Revision history for this message
David Suffield (david-suffield) wrote :

I understand your point. The compressed tar ball is not as small as it could be, but gziped files work better with automake and packages.

The gziped files are mostly PPDs. If PPDs are not gziped in the tar ball then they need to be gziped in a post-install hook. Post-install hooks don't work will at uninstall time because the file names have changed.

It is much cleaner to list gziped PPDs explicitly in the tar ball and let automake do the right thing with no post-install hooks.

Revision history for this message
Tim Waugh (twaugh) wrote :

I don't think that's the case. List the files as 'whatever.gz' in Makefile.am and let it compress them at build time, i.e. have the compressed files as build targets.

Revision history for this message
David Suffield (david-suffield) wrote :

Good idea :)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.