So perhaps tar should allow subsequent (as opposed to recursive) reads of
the same file?
Ahh, I see now what happens there :), thanks. Yes. That would make
sense.
.. do we really need to parse all options? Wouldn't it be better to
artificially bound the -T FILE parsing power? I mean, this
Hi Pavel,
.. do we really need to parse all options? Wouldn't it be better to
artificially bound the -T FILE parsing power? I mean, this is starting to
have Turing machine power :)
Well, basically, it provides a convenient way to store tar
command lines into a kind of configuration files:
Pavel Raiskup prais...@redhat.com ha escrit:
14:16:20 /tmp$ rm -rf tar
14:16:35 /tmp$ git clone git://git.savannah.gnu.org/tar.git /dev/null
14:16:53 /tmp$ cd tar
14:16:55 /tmp/tar$ ( ./bootstrap ./configure make -j5 ) /dev/null
Thanks, I see the problem now.
Regards,
Sergey
Hi,
Am 16.08.2013 um 10:26 schrieb lixiangyu2...@gmail.com
lixiangyu2...@gmail.com:
CatchEA31.jpg
Catch38FA.jpg
Catch3FF7.jpg
All these files cannot be unpacked，unless rename it
Catch515F.jpg
Try adding --force-local. See for details
Sergey Poznyakoff g...@gnu.org.ua ha escrit:
14:16:55 /tmp/tar$ ( ./bootstrap ./configure make -j5 ) /dev/null
Thanks, I see the problem now.
Fixed in repository. Please pull.
Regards,
Sergey
