Open gyakovlev opened 3 years ago
The main changes required for this to work should be on cargo.eclass. There should be a variable similar to CRATES
to allow the maintainer to add vendored dependency paths relative to the workdir. It could be done by generating (or modifying) the .cargo/config
file so cargo can handle those dependencies.
I suppose this covers the case I mentioned in https://github.com/projg2/pycargoebuild/issues/14#issue-1557734676 wrt pkgcraft-c's '../pkgcraft' dep too?
Not really, that’s different. It’s already working fine if you invoke cargo(eclass included) properly.
Sometimes a project uses a git dependency. cargo-ebuild should handle simple cases of git deps.