If you used add with dev + a relative path an absolute path ends up on Manifest.toml / meta.json

[oxinabox]

If i do something like

juliapkg.add("PowerfulCore", dev=True, , path="../../julia/PowerfulCore/")

to add a julia dependency to a python package within a monorepo then it installs and works correctly.
But the Manifest.toml / meta.json end up with a relative path in it.

This is technically fine as when i checkout the repo in a new location it just updates to the new path.
But it means that if I version control this file it has a lot of meaningless changes.

Manifest.toml's do support relative paths.

[cjdoris]

Sure, but a relative path in Manifest.toml is relative to that file (in some Julia environment), whereas a relative path in juliapkg.json is relative to that file (in your package). These two places could be completely unrelated parts of your filesystem, so it wouldn't really be much use to make the relative path reaching all the way over.

[oxinabox]

Assuming the Manifest.toml is somewhere sensible*
the function relpath can be used to relocate a path that is relative to the the juliapkg.json to one relative to the Manifest.toml. Which would still be something sensible and valid on multiple locations.

• https://docs.python.org/3/library/os.path.html#os.path.relpath
• https://docs.python.org/3/library/pathlib.html#pathlib.PurePath.relative_to
• https://docs.julialang.org/en/v1/base/file/#Base.Filesystem.relpath

* which it must be if you end up version controlling it since both it and the juliapkg.json must be in a single version controlled folder if you care about this

[cjdoris]

Yeah I know about relpath. My issue is with the assumption you stated - it's not always true. But maybe in some circumstances we do know the two locations are related and we can do this.