From: flameeyes@gmail.com (Diego 'Flameeyes' Pettenò)
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: RFC: lzma tarball usage
Date: Thu, 08 May 2008 16:30:22 +0200 [thread overview]
Message-ID: <m263to6f7l.fsf@gmail.com> (raw)
In-Reply-To: 20080508143606.67bcfe6e@snowcone
[-- Attachment #1: Type: text/plain, Size: 953 bytes --]
Ciaran McCreesh <ciaran.mccreesh@googlemail.com> writes:
> You miss my point. GNU tar sometimes changes its on disk format (and
> will be doing so again at some point for xattrs)
It's not really important to the discussion, but...
The TAR format is designed as such that on disk formats can be extended
without breaking entirely backward compatibility. For what it's worth,
extended attributes and ACLs are already supported by star (Schilling's)
and bsdtar (libarchive). The fact that GNU tar doesn't support them at
the moment is a different problem. On the other hand, even if the GNU
tar does not support reading those attributes, it does handle them
gracefully, warning the user of unknown extended headers, and then
proceeding to unpack the data without preserving the extended
attributes.
So what Doug said stands perfectly and does not interest GNU tar at all.
--
Diego "Flameeyes" Pettenò
http://blog.flameeyes.eu/
[-- Attachment #2: Type: application/pgp-signature, Size: 196 bytes --]
next prev parent reply other threads:[~2008-05-08 14:30 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 13:23 [gentoo-dev] RFC: lzma tarball usage Mart Raudsepp
2008-05-07 13:34 ` Fabian Groffen
2008-05-08 18:45 ` Mart Raudsepp
2008-05-08 19:09 ` Fabian Groffen
2008-05-08 19:17 ` Santiago M. Mola
2008-05-08 19:21 ` Mart Raudsepp
2008-05-17 15:55 ` Enrico Weigelt
2008-05-10 7:32 ` Mike Frysinger
2008-05-10 7:36 ` Fabian Groffen
2008-05-10 9:57 ` Mike Frysinger
2008-05-07 14:12 ` Natanael Copa
2008-05-07 14:55 ` Ulrich Mueller
2008-05-08 8:06 ` [gentoo-dev] " Duncan
2008-05-08 10:49 ` Diego 'Flameeyes' Pettenò
2008-05-08 10:59 ` Graham Murray
2008-05-08 11:31 ` Diego 'Flameeyes' Pettenò
2008-05-08 11:41 ` Ulrich Mueller
2008-05-07 14:53 ` [gentoo-dev] " Benedikt Morbach
2008-05-07 15:03 ` Ulrich Mueller
2008-05-07 15:02 ` Benedikt Morbach
2008-05-07 16:06 ` Chris Gianelloni
2008-05-07 18:38 ` Enrico Weigelt
2008-05-07 20:01 ` Richard Freeman
2008-05-07 20:10 ` Doug Goldstein
2008-05-08 0:52 ` [gentoo-dev] " Ryan Hill
2008-05-08 13:17 ` Doug Goldstein
2008-05-08 13:28 ` Ciaran McCreesh
2008-05-08 13:32 ` Doug Goldstein
2008-05-08 13:36 ` Ciaran McCreesh
2008-05-08 13:43 ` Doug Goldstein
2008-05-09 8:37 ` James Cloos
2008-05-08 14:30 ` Diego 'Flameeyes' Pettenò [this message]
2008-05-08 13:41 ` Doug Goldstein
2008-05-08 14:33 ` Robert Buchholz
2008-05-09 1:04 ` Ryan Hill
2008-05-08 11:30 ` [gentoo-dev] " Luca Barbato
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m263to6f7l.fsf@gmail.com \
--to=flameeyes@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox