Project.toml with dev used

General Usage
1

I have a package that has dependencies on packages from the General registry and other packages developed here. The output of the Pkg.status command is:

Status `C:\Users\jakez\.julia\dev\Foo\Project.toml`
  [a93c6f00] DataFrames v1.7.0
  [f686b519] Bar1 v0.1.0 `C:\Users\jakez\.julia\dev\Bar1`
  [89398ba2] LocalRegistry v0.5.7
  [f27b6e38] Polynomials v4.0.12
  [be4cc790] Bar2 v0.1.1 `..\Bar2`
  [2913bbd2] StatsBase v0.34.4
  [41c3b3d0] Bar3 v0.1.0 `..\Bar3`
  [49faafe7] Bar4 v0.1.0 `..\Bar4`

Why is the path to Bar1 an absolute path, and the path to Bar2, Bar3 & Bar4 relative paths?

I much prefer relative paths, as I do development on a number of computers and this is more convenient.

I have not checked, but when checking into git will it convert an absolute path to a relative path?

2

No, the absolute path is set when you dev a directory. If you dev a git repo, the default is to put it in ~/.julia/dev, though you can change this behavior by using the --local argument for the dev command.

See also

And

3

Okay I get it now. It is …\Bar2 because I typed in dev ..\Bar2 and it it is Bar1 v0.1.0 C:\Users\jakez.julia\dev\Bar1`` because I typed in 'dev \Users\jakez.julia\dev\Bar1`.

From the manual you referenced:

In addition to absolute paths, add and dev can accept relative paths to packages. In this case, the relative path from the active project to the package is stored. This approach is useful when the relative location of tracked dependencies is more important than their absolute location.