Can't use zopen from one rootfs to create another rootfs.

[covener]

I am on 0.3.0-dt-stable

I think It should be possible to run zopen init an additional time even when another zopen-config has been sourced.
Alternatively, the 2nd zopen init should provide better feedback about the limitation.

My use case for ZOT: One set of tools safe to load in interactive shells, another that is meant only for some specific build environment.

Currently, the zopen init running in the first env (/u/WASTST1/zopen-dt/) reports this:

...
- Check for shipped curl pax
/u/WASTST1/zopen-dt/usr/packages/curl-8.1.2.20230707_145137.zos.pax.Z
- Found packages/curl-8.1.2.20230707_145137.zos.pax.Z. Adding to zopen cache to install as bootstrap
- Check for shipped jq pax
- Found packages/jq-1.6.20230720_160648.zos.pax.Z. Adding to zopen cache to install as bootstrap
***ERROR: Could not locate default cacert.pem at '../cacert.pem'.

Running meta-dt-0.5.0/bin/zopen with the same environment works

[DevonianTeuchter]

Recreated locally. Issue is due to the hardcoded location of the CA certificate - that is fine for the first zopen init after unpax/clone however afterwards from within a zopen environment that location will not exist.

[DevonianTeuchter]

PR merged to main that should resolve this