summaryrefslogtreecommitdiff
path: root/pcr/jmdns
diff options
context:
space:
mode:
authorDenis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>2020-02-08 16:18:44 +0100
committerDenis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>2020-02-08 16:35:38 +0100
commit889d759a4d3eb96e4ab0c12c5391480905304e09 (patch)
treedd621eb0225716f4597edac57eb9a7cb263e5873 /pcr/jmdns
parentfc18dd0bbb82847bbe07215951b998480c11dc42 (diff)
downloadabslibre-889d759a4d3eb96e4ab0c12c5391480905304e09.tar.gz
abslibre-889d759a4d3eb96e4ab0c12c5391480905304e09.tar.bz2
abslibre-889d759a4d3eb96e4ab0c12c5391480905304e09.zip
libre: Add phoronix-test-suite-libre
This doesn't contain any tests yet. Some could be added back by not deleting them from ob-cache/. Tests like build-gcc should be OK to bring back as they only consists in downloading the GCC source code, checking its checksum, and compiling it. Since GCC is fully free software and that they use the official releases, it should be safe to bring them back. Some other tests are more problematic: - Some tests like build-linux use source code is not fully free. This should be removed. Using linux-libre instead would be possible, but a different test would need to be written for that. - Some like xonotic uses official binaries, which is a problem since we might want not to trust binaries, and we also don't know how they were built, so we cannot ensure that they are buildable on FSDG distributions. Again such tests would need to be removed or forked not to create problematic test results. - Some like build-imagemagick download source code from the phoronix-test-suite website. To use that we would need to ensure that the released source code is the same than the one released by the upstream project. If not we could either remove theses tests or patch the official source to reproduce an equivalent tarball in a way that can be more easily reviewed. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
Diffstat (limited to 'pcr/jmdns')
0 files changed, 0 insertions, 0 deletions