[PATCH 2/3] tar01 and tar02: Do not generate tar archives
Sebastian Huber
sebastian.huber at embedded-brains.de
Wed Nov 20 14:44:46 UTC 2019
On 20/11/2019 15:39, Sebastian Huber wrote:
> On 20/11/2019 00:52, Chris Johns wrote:
>>>> I am concerned we are loosing some of the checking that we currently
>>>> have moving
>>>> to this approach. The symlink issue is a real one so maybe we hold a
>>>> single tar
>>>> to check that works.
>>> With the dynamic generation of the archive we cannot test the file
>>> permissions,
>>> the group and user IDs, and the time stamps.
>> Ah yes this is a good point. Could we have a single tar file that
>> tests those
>> parts and others that are generated to test the host and RTEMS code?
>
> At the moment my only concern is the new build system. I have to focus
> to get this integrated since I don't want to reiterate the conversion
> due to changes in the RTEMS sources which may take place in the meantime.
>
> There are some issues with waf and pax. Waf doesn't like directories as
> nodes. You have to use files. If you only feed files into pax, you end
> up with:
>
> $ tar tf build/sparc/erc32/testsuites/libtests/tar01/tar01.tar
> home/test_file
> home/test_script
> symlink
>
> Which leads to:
>
> https://devel.rtems.org/ticket/3823
>
> I think we have to fix our tar support first to make any progress here.
> This will delay my build system work and I am currently very busy with
> other things. The question is if we should start integrating it without
> the tests which depend on tar.
Just for reference, here are the two tar tests which I struggle to convert:
https://git.rtems.org/sebh/rtems.git/tree/spec/build/testsuites/libtests/RTEMS-BUILD-TEST-LIB-TAR01.yml?h=build
https://git.rtems.org/sebh/rtems.git/tree/spec/build/testsuites/libtests/RTEMS-BUILD-TEST-LIB-TAR02.yml?h=build
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.huber at embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
More information about the devel
mailing list