actually, the first solution is the good one.
The command to list the installed conda packages, and put them in a file, is managed by a parent POM (i.e., dcs-python-parent). Then, it also includes a postinstall scriptlet section, to install them during the post install phase of the Application’s RPM.
It’s automatically done, leveraging the parent POM mentioned above.
We support a list of channels, and you can get the list with
sudo conda info.
We recently added the support for conda-forge, with the lowest priority (because it’s not stable enough).
If you want to see the full processed POM, you can use the following command:
Hope this helps,
the Operations Support team at Terradue