move tests to info directory when packaging

[boldorider4]

This PR originates from the request that tests are moved to the info directory inside the produced package
in order to let rattler-build behavior conform of that of conda-build.

The request is documented in this issue.

[wolfv]

I get the idea but I am not sure this would work easily because of:

• how tests are run (we set the CWD to the directory with the files in
• tests need to be backward compatible (we need to be able to run tests with the old format, too, for downstream tests etc.)

As mentioned in the discussion, I think I would be even more excited about a way to split off test files into additional packages.

[boldorider4]

how tests are run (we set the CWD to the directory with the files in

can you complete the sentence?

[JeanChristopheMorinPerso]

Hi @wolfv, we would also like to have a talk about splitting the tests into a different artifact. But we think that we still need to fix the issue at hand, which is that the tests should not go in /etc. I would view this as a stop gap kind of thing while we can start/have a discussion on how to go abut moving the tests into a different artifact.

As for backward compatibility, I think it should be doable to change rattler-build to look for tests in info, and fallback to etc in cases where the artifact was generated with the old behavior.

Would that solve your concern(s)?

[wolfv]

I am sure we can make it work. But the reason we moved the test files out of the info folder is also still valid - we don't want to unecessarily blow up the size of the 'metadata' files.

We could also create a third archive in the .conda file that would contain test files. Or we could sort info/test files into the pkg-... archive in the .conda file but that would make things slightly more complicated.