On 18/11/19 6:10 pm, Sebastian Huber wrote: > This simplifies the build and avoids some host dependencies, e.g. > availability of symbolic links in the host file system. Makes it > possible to validate time stamps. > > Update #3818. > --- > testsuites/libtests/Makefile.am | 41 > ++++++++------------------------- > testsuites/libtests/tar01/tar01.tar | Bin 0 -> 10240 bytes > testsuites/libtests/tar01/tar01.tar.gz | Bin 0 -> 296 bytes > testsuites/libtests/tar01/tar01.tar.xz | Bin 0 -> 340 bytes > testsuites/libtests/tar02/tar02.tar | Bin 0 -> 10240 bytes > 5 files changed, 9 insertions(+), 32 deletions(-) > create mode 100644 testsuites/libtests/tar01/tar01.tar > create mode 100644 testsuites/libtests/tar01/tar01.tar.gz > create mode 100644 testsuites/libtests/tar01/tar01.tar.xz > create mode 100644 testsuites/libtests/tar02/tar02.tar
How are the tar files created? How do we capture what is in them and how to regenerate them? At the moment I can inspect all of this test via cgit. The idea of downloading and checking can be problematic depending on the host and set up, ie a tablet. Has the generation of these files been checked on more than Linux? How do we check updated host tools have not broken the code we have in RTEMS? 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. Chris _______________________________________________ devel mailing list [email protected] http://lists.rtems.org/mailman/listinfo/devel
