On Tue, Aug 18, 2020 at 5:52 PM Chris Johns <chr...@rtems.org> wrote:
> On 18/8/20 9:16 pm, Sebastian Huber wrote:
> > This patch is for the new build system.
>
> <stand><clap><clap><clap>
>
> Looking forward to this change.
>
Me too.
We determined that the Python tar defaulted to " POSIX.1-2001 (pax) format"
which is newer than the "IEEE Std 1003.2 (“POSIX.2”)" from the pax man
page as ustar as best I can tell. But GNU tar describes the formats as:
-H, --format=FORMAT
create archive of the given format
FORMAT is one of the following:
gnu GNU tar 1.13.x format
oldgnu GNU format as per tar <= 1.12
pax POSIX 1003.1-2001 (pax) format
posix same as pax
ustar POSIX 1003.1-1988 (ustar) format
v7 old V7 tar format
tar and pax seem to conflict. Wikipedia is clear it is the ustar. But GNU
tar
seems to be giving pax credit for a newer format I don't see supported.
Are we sure the POSIX-2001 (pax) format is definitely different from
what pax was using which I think is the 1988 ustar format.
And can the RTEMS side untar read the newer format?
Switching tars is a no brainer and updating the format is also as long
as we are really updating and keeping things in sync.
--joel
> Thanks
> Chris
> _______________________________________________
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
>
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
