Skip to contentSkip to conversation

Remove old build scripts

RFC PATCH New Petr Vorel 2 participants 3 messages Apr 24, 2018 – Apr 27, 2018

lore
Share & tools
lore

Petr Vorel

author
#0 lore raw

RFC PATCH 1/1 Remove old build scripts

These scripts are from CVS era, expect git://ltp.git.sourceforge.net.
Although they have support for git and testing our make build system it's important, we use travis and anything important should be moved there.

---
BTW: my wish is to move from custom make build system to automake based.
Why: 'make install' for Open POSIX testsuite is broken (some files are missing) and due being moved-in as sort of sub-project it's not easy to fix it. And we use autoconf anyway.

Kind regards,
Petr

---
 testscripts/build/README                           |  71 ------
 testscripts/build/build_test_function.sh           | 243 ---------------------
 testscripts/build/default_runtest_set.awk          |  44 ----
 testscripts/build/ltp-missing-install-files.py     | 116 ----------
 testscripts/build/test_install_in_build_tree.sh    |  47 ----
 .../build/test_install_out_of_build_tree.sh        |  49 -----
 testscripts/build/test_out_of_build_tree.sh        |  51 -----
 7 files changed, 621 deletions(-)
 delete mode 100755 testscripts/build/README
 delete mode 100755 testscripts/build/build_test_function.sh
 delete mode 100755 testscripts/build/default_runtest_set.awk
 delete mode 100755 testscripts/build/ltp-missing-install-files.py
 delete mode 100755 testscripts/build/test_install_in_build_tree.sh
 delete mode 100755 testscripts/build/test_install_out_of_build_tree.sh
 delete mode 100755 testscripts/build/test_out_of_build_tree.sh
testscripts/build/README deleted +0 -71
deleted file mode 100755
index e3c3190c0..000000000
@@ -1,71 +0,0 @@
-This scripts contains any and all scripts which will help in testing the make
-infrastructure.
-
-A brief description is as follows:
-
-Foundation Build Regression Test Scripts:
-
-- build_test_functions.sh	    -	Generic library functions for all
-					pull / build / test scenarios.
-
-There are a total of 3 different positive pull / build / test scenarios that
-have been identified which should be tested on a regular basis, both prior to
-and after commit:
-
-- test_install_in_build_tree.sh     -	Build in srcdir, install in srcdir.
-- test_install_out_of_build_tree.sh -	Build in srcdir, install in
-					rootfs / outside of builddir // srcdir.
-- test_out_of_build_tree.sh         -	Build outside of srcdir, install in
-					rootfs / outside of builddir // srcdir.
-
-The scenarios are defined in include/mk/env_pre.mk (look for BUILD_TREE_STATE).
-
-These scenarios all fulfill the following requirements:
-1. Pull LTP from a predefined SCM (cvs is the only method supported today, but
-   other SCMs could be added when and if support is properly enabled by the
-   project admins).
-2. Apply a custom -p0'able patch if defined with LTP_PATCH (THIS MUST BE THE
-   ABSOLUTE PATH TO THE PATCH!!!).
-3. Configure (make autotools -> configure).
-4. Compile (make all).
-5. Install (make install).
-6. Test (execltp -v).
-
-If you want to add another scenario, please email the list requesting the
-enhancement and we'll see what we can do to accomodate it if the scenario
-functionally makes sense.
-
-You can use a variety of variables to control how things operate, such as:
-
-- CLEAN_TEMPFILES	- !1 - don't clean up the temporary generated files
-			  after the scenario is complete.
-			- 1 - clean up the temporary generated files after the
-			  scenario is complete.
-- MAKEFLAGS		- flags which will be passed directly into make
-			  (please ensure that any and all options passed are
-			  properly escaped beforehand if quoted).
-- TMPDIR		- base temporary directory for all generated and
-			  pulled files.
-
-About the warning...
-
-If you see:
-
-	WARNING: Read the [.../]README before executing this script [...]!
-
-this is by design. I inserted this in the script to intentionally underscore
-the fact that folks need to be very careful when executing this script and
-exercise the following common sense:
-
-1. Use a chroot, or lower-privileged user (preferrably a test user). If there's
-   a bug in the make infrastructure, you could end up eating crow after your
-   build host gets hosed!
-2. Properly chmod your files / directories! You shouldn't have 00777 set on
-   anything that you don't mind parting with, or you are begging for trouble!
-
-   set I_HAVE_READ_THE_README_WARNING to 1 in your environment in order to
-   proceed.
-
-Utilities:
-- ltp-missing-install-files.py - A script which does a real basic first cut at
-				 trying to find missing commands or test files.
testscripts/build/build_test_function.sh deleted +0 -243

243 lines not on this page · raw message

testscripts/build/default_runtest_set.awk deleted +0 -44

44 lines not on this page · raw message

testscripts/build/ltp-missing-install-files.py deleted +0 -116

116 lines not on this page · raw message

testscripts/build/test_install_in_build_tree.sh deleted +0 -47

47 lines not on this page · raw message

testscripts/build/test_install_out_of_build_tree.sh deleted +0 -49

49 lines not on this page · raw message

testscripts/build/test_out_of_build_tree.sh deleted +0 -51

51 lines not on this page · raw message

Signature · 1 line
2.16.3
#1 lore raw

RFC PATCH 1/1 Remove old build scripts

Hi!

Quoted 4 lines

These scripts are from CVS era, expect git://ltp.git.sourceforge.net.
Although they have support for git and testing our make build system it's important, we use travis and anything important should be moved there.

I do agree here, let's apply this, unless anybody objects, next week.

Quoted 6 lines

---
BTW: my wish is to move from custom make build system to automake based.
Why: 'make install' for Open POSIX testsuite is broken (some files are missing) and due being moved-in as sort of sub-project it's not easy to fix it. And we use autoconf anyway.

I do not like automake that much. To be honest I think that the whole autotools suite is years behind the rest of the world, hence I would consider moving to it to be a step back.

Signature · 2 lines
Cyril Hrubis
[email protected]
author
#2 lore raw

RFC PATCH 1/1 Remove old build scripts

In reply to Petr Vorel

Hi,

Quoted 7 lines

These scripts are from CVS era, expect git://ltp.git.sourceforge.net.
Although they have support for git and testing our make build system it's important, we use travis and anything important should be moved there.

---

Merged.

Kind regards,
Petr