* Use --format=pax for release?
@ 2011-03-31 6:45 Ian Lance Taylor
2011-03-31 16:00 ` Joe Buck
0 siblings, 1 reply; 3+ messages in thread
From: Ian Lance Taylor @ 2011-03-31 6:45 UTC (permalink / raw)
To: gcc
Our releases are normally built with GNU tar, which seems to default to
--format=tar. I wonder if we should switch to --format=pax. The pax
format was defined by POSIX.1 10 years ago, and should be widely
supported at this point. GNU tar can generate it and recognize it.
That might permit us to remove this paragraph from install.texi:
@item GNU tar version 1.14 (or later)
Necessary (only on some platforms) to untar the source code. Many
systems' @command{tar} programs will also work, only try GNU
@command{tar} if you have problems.
Ian
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Use --format=pax for release?
2011-03-31 6:45 Use --format=pax for release? Ian Lance Taylor
@ 2011-03-31 16:00 ` Joe Buck
2011-03-31 21:07 ` Ian Lance Taylor
0 siblings, 1 reply; 3+ messages in thread
From: Joe Buck @ 2011-03-31 16:00 UTC (permalink / raw)
To: Ian Lance Taylor; +Cc: gcc
On Wed, Mar 30, 2011 at 11:38:02PM -0700, Ian Lance Taylor wrote:
> Our releases are normally built with GNU tar, which seems to default to
> --format=tar. I wonder if we should switch to --format=pax. The pax
> format was defined by POSIX.1 10 years ago, and should be widely
> supported at this point. GNU tar can generate it and recognize it.
I've never seen anyone distribute free software with the pax format.
Yes, Posix created it to settle a fight between promoters of the tar
and the cpio format: create yet a third format and declare peace
(pax is Latin for peace). But no one uses pax.
> That might permit us to remove this paragraph from install.texi:
>
> @item GNU tar version 1.14 (or later)
>
> Necessary (only on some platforms) to untar the source code. Many
> systems' @command{tar} programs will also work, only try GNU
> @command{tar} if you have problems.
But you'd need a program that could deal with the pax format, which, for
most people, would be GNU tar.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Use --format=pax for release?
2011-03-31 16:00 ` Joe Buck
@ 2011-03-31 21:07 ` Ian Lance Taylor
0 siblings, 0 replies; 3+ messages in thread
From: Ian Lance Taylor @ 2011-03-31 21:07 UTC (permalink / raw)
To: Joe Buck; +Cc: gcc
Joe Buck <Joe.Buck@synopsys.COM> writes:
> On Wed, Mar 30, 2011 at 11:38:02PM -0700, Ian Lance Taylor wrote:
>> Our releases are normally built with GNU tar, which seems to default to
>> --format=tar. I wonder if we should switch to --format=pax. The pax
>> format was defined by POSIX.1 10 years ago, and should be widely
>> supported at this point. GNU tar can generate it and recognize it.
>
> I've never seen anyone distribute free software with the pax format.
> Yes, Posix created it to settle a fight between promoters of the tar
> and the cpio format: create yet a third format and declare peace
> (pax is Latin for peace). But no one uses pax.
>
>> That might permit us to remove this paragraph from install.texi:
>>
>> @item GNU tar version 1.14 (or later)
>>
>> Necessary (only on some platforms) to untar the source code. Many
>> systems' @command{tar} programs will also work, only try GNU
>> @command{tar} if you have problems.
>
> But you'd need a program that could deal with the pax format, which, for
> most people, would be GNU tar.
The question is whether the tar program on other operating systems is
more likely to support the pax format or the GNU tar format.
If the tar program on other systems does not support the pax format,
then I agree this would be useless.
Ian
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2011-03-31 16:00 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-03-31 6:45 Use --format=pax for release? Ian Lance Taylor
2011-03-31 16:00 ` Joe Buck
2011-03-31 21:07 ` Ian Lance Taylor
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).