Hi Steffen! On Mon, 23 Mar 2009 00:05:08 +0100, Steffen Moeller wrote: > Luca Capello wrote: >> And I am lost: it seems that while the "correct" tar is the one in >> /usr/local/bin/tar [2], install.sh still uses /bin/tar. Has anyone any >> clue about this behavior? > > I (think to) have just fixed this with my latest commit of install.sh.
You missed some /tmp, just fixed: http://git.debian.org/?p=pkg-fso/files.git;a=commitdiff;h=46fda86ce5ecdfb3937b867c0bafbd2cd82ec125 > That said, I think a minimal tar that does not understand -z or -C > would be sufficient. > > tar -xz -C / -f sometarfile.gz > > then becomes > > gzip -cd sometarfile.gz | (cd / && tar -xf -) The second part could suffer of the same BASH problem we found for ar (which I have not forgot, do not worry): http://lists.alioth.debian.org/pipermail/pkg-fso-maint/2009-March/000893.html > which might not be as neat but works with all the versions of tar out there. > Suggestions? We would not need to download additional packages, then. This will do the trick, for sure, and it will fix the issue once for all. However, I still consider tar not supporting -z/-j a bug, since this is very well known and used feature. Feel free to fix it as you like, if it works as expected I really do not care now that I stated my opinion ;-) Thx, bye, Gismo / Luca
pgpxcD4BYSca7.pgp
Description: PGP signature
_______________________________________________ pkg-fso-maint mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/pkg-fso-maint
