Individual compression vs. tar.gz (was: Bug#4834: magicfilter's examples should be archived individually)
I'd like to hear your (debian-devel) input on the following, since I'm
unsure how to proceed:
Susan G. Kleinmann reported on 17 Oct 1996 the following bug-report:
------- Forwarded Message
Package: magicfilter
Version: 1.2
The sample files for magicfilter are in
/usr/doc/examples/magicfilter/filters/filters.tar.gz.
Because they are gzipd' into a single tar file, rather than untar'd and
gzip'd individually (they're so small I don't see why gzip'ing is
important anyway), they are hidden in the Contents.gz file.
Suggestion: They should be left gunzip'd and should be included
individually in /usr/doc/examples/magicfilter (or the appropriate directory
in the new packaging standards).
Susan Kleinmann
------- End of Forwarded Message
If I do what Susan suggests, I get the following:
(david@eos) /tmp/filters$ls -l /usr/doc/magicfilter/examples/filters/filters.tar.gz ; mkdir filters; cd filters; tar xvzf /usr/doc/magicfilter/examples/filters/filters.tar.gz; du
-rw-r--r-- 1 root root 7901 Jan 18 14:53 /usr/doc/magicfilter/examples/filters/filters.tar.gz
bj10e-filter
bj200-filter
cps300-filter
cps400-filter
cps600-filter
cpsonly300-filter
cpsonly400-filter
cpsonly600-filter
deskjet-filter
dj500c-filter
dj500-filter
dj550c-filter
epson9c-filter
epson9-filter
epsonlqc-filter
epsonlq-filter
ibmpro-filter
jetp3852-filter
la50-filter
la75-filter
laserjet-filter
laserjetlo-filter
lbp8-filter
lj250-filter
ljet2p-filter
ljet2plo-filter
ljet3-filter
ljet4-filter
ljet4l-filter
ljet4m-filter
ljet4ml-filter
ljetplus-filter
ljetpluslo-filter
ln03-filter
m8510-filter
necp6-filter
oki182-filter
pj-filter
pjxl300-filter
pjxl-filter
ps300-filter
ps400-filter
ps600-filter
psonly300-filter
psonly400-filter
psonly600-filter
r4081-filter
stylus800-filter
stylus_color_360dpi-filter
stylus_color_720dpi-filter
tek4693-filter
tek4696-filter
264 .
i.e. the resulting directory would be 264kB large vs. 8kB (33-fold
increase). Is this tolerable and if not, how should I proceed with
the bug report? Do we have an bug-report status 'dismissed' for bug
reports which are not handled and never will be?
David
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: