The development of the recipes for autoconf/automake/libtool showed a hole in the CI process:
the CI does not detect embedded build-system dependent paths in the generated packages.
That's why I propose to run the test_package tests in a different conan home.
This would require to run the tests with a different CONAN_USER_HOME and CONAN_USER_HOME_SHORT environment variable.
Also, the generated packages (+ its dependencies) should be copied to the new conan home.
Additionally, care should be taken for packages in CONAN_USER_HOME_SHORT, that its random subdirectory is randomized again.
@uilianries
While working on the bison recipe, this issue emerged again.
The bison binary can hold a hardcoded path to m4.
https://github.com/bincrafters/conan-center-index/pull/9
To test whether the relocatable thing was working ok, I had to do the following things:
conan create . bison/3.5.3@conan_server and upload the bison recipe conan upload -r local --all bison/3.5.3@~/.conan to ~/conan_tmpCONAN_USER_HOME to /tmp/conan remove -f bison/3.5.3@conan test /path/to/bison/test/package bison/3.5.3@ -tbf /tmp/test_bisonThis should be tested by CCI.
@madebr Thanks for sharing the steps!
Most helpful comment
@uilianries
While working on the bison recipe, this issue emerged again.
The bison binary can hold a hardcoded path to
m4.https://github.com/bincrafters/conan-center-index/pull/9
To test whether the relocatable thing was working ok, I had to do the following things:
conan create . bison/3.5.3@conan_serverand upload the bison recipeconan upload -r local --all bison/3.5.3@~/.conanto~/conan_tmpCONAN_USER_HOMEto/tmp/conan remove -f bison/3.5.3@conan test /path/to/bison/test/package bison/3.5.3@ -tbf /tmp/test_bisonThis should be tested by CCI.