equivalent of Manifest.toml / pixi.lock

[oxinabox]

As i understand it the juliapkg.json roughly coresponds to the Project.toml or pixi.toml.
It specified compatibility ranges of direct dependencies.
The Manifest.toml / pixi.lock exist to ensure you can exactly get the same version of things that another user was using and testing, including indirect dependencies.
For Pkg this is done via using ] instantiate instead of ] resolve.
For pixi.lock this is done via the --frozen or --locked flags passed to pixi install
As far as I can tell there is no equivalent for pyjuliapkg

A Manifest.toml, meta.json files are created as part of install process.
But if already present they are ignored and recreated every time AFAICT. (cf #77)

[cjdoris]

Yes we currently delete the Manifest.toml before resolving. I can't totally remember why but I think that Pkg gets in a tizz with the specific sequence of commands we do in resolve() after some edits to Project.toml.

Ideally we'd keep it before resolving, which should make resolving faster. Will need to resolve the above issue though.

As for having lock files - we could store a copy of Manifest.toml in meta.json, and call it lock.json instead, and make lock.json a documented file that you could put in version control.