As observed here, the naive approach to find and load all .janno files (with the d() pseudo-function) became increasingly less useful with the recent changes to trident. It is now increasingly more likely that users maintain archives with multiple package versions.
I think we should switch to the mechanism used by trident: Search for POSEIDON.yml files and load the .janno files with the relative paths in them. This can be done in a much more minimal way compared to trident, but it should include a filter operation to only consider the latest versions for a given package.
As observed here, the naive approach to find and load all .janno files (with the
d()pseudo-function) became increasingly less useful with the recent changes to trident. It is now increasingly more likely that users maintain archives with multiple package versions.I think we should switch to the mechanism used by trident: Search for POSEIDON.yml files and load the .janno files with the relative paths in them. This can be done in a much more minimal way compared to trident, but it should include a filter operation to only consider the latest versions for a given package.