1 |
Neil Bothwick <neil@××××××××××.uk> wrote: |
2 |
|
3 |
> On Tue, 06 May 2008 14:40:08 +0200, Michael Schmarck wrote: |
4 |
> |
5 |
>> > That hasn't been needed for a long time. Tar is able to detect bzip2 |
6 |
>> > and gzip compression and handle it automatically. |
7 |
>> |
8 |
>> That's only true for GNU tar. If you're also dealing with other |
9 |
>> systems where you might not have GNU tar, you might be "surprised" |
10 |
>> to find that "tar xvf file.tgz" doesn't work. |
11 |
> |
12 |
> However, this thread is specifically about using tar on /Gentoo, which |
13 |
> does use GNU tar. |
14 |
|
15 |
Well, nonetheless I think that it's a bad idea to get too used to |
16 |
GNUisms. Especially, if there are so easy "workarounds". |
17 |
|
18 |
>> Hence I think, that it is a good idea to keep on using z or j. |
19 |
> |
20 |
> That really depends on the level of portability your scripts need. Using |
21 |
> z or j is more portable, but also more complex for scripting. |
22 |
|
23 |
That's rather a question of how complex the "environment" is, that the |
24 |
script needs to deal with. If you really want to throw all different |
25 |
sort of things at your script (like .tar.gz, .tar.Z, .tar.bz2, .tar.lzma), |
26 |
then yes, the script would get more complex. |
27 |
|
28 |
Michael |
29 |
|
30 |
-- |
31 |
gentoo-user@l.g.o mailing list |