Path and Git dependencies for rebar3 packages

[foxfriends]

I have an Erlang package that I wish to test linked to a Gleam project, but this Erlang package is not published on Hex. If this was a Gleam package, I would be able to include it using my_package = { path = "../my-package" } but I it seems when such a package does not contain gleam.toml, it is considered invalid.

Whatever logic that is used to make a non-Gleam package from Hex work, could that be applied to a non-Gleam package from path or git dependencies so all three work the same way?

[lpil]

Whatever logic that is used to make a non-Gleam package from Hex work, could that be applied to a non-Gleam package from path or git dependencies so all three work the same way?

For packages on Hex the details of the packages are fetched from Hex itself. Hex doesn't know anything about path and git packages, so we need some other way to get this information.

For Gleam projects we can read gleam.toml, but rebar3 and mix config is more complex and cannot be simply read, so we cannot easily do the same for them.

What's the package you wish to use from Gleam?

[foxfriends]

In my case I was modifying pgo and wanted to test the changes I made on my Gleam project (and to continue my Gleam project because it is fun!). Since I was unable to include my modified version of pgo, I have to wait for it to be published to Hex instead.

[lpil]

Thank you