On Wed, Feb 17, 2021 at 9:33 PM Johannes Schauer Marin Rodrigues <jo...@debian.org> wrote: [...] > And then I run "cargo build". Every time I get a message like: > > error: no matching package named `foo` found > > I install librust-foo-dev until finally: > > Parent pid 535147, child pid 535148 > Child process initialized in 30.93 ms > Compiling proc-macro2 v1.0.18 > Compiling unicode-xid v0.2.0 > Compiling syn v1.0.12 > Compiling dotenv v0.15.0 (/tmp/dotenv/dotenv) > Compiling quote v1.0.7 > Compiling proc-macro-hack v0.5.9 > Compiling dotenv_codegen_implementation v0.15.0 > (/tmp/dotenv/dotenv_codegen_implementation) > Compiling dotenv_codegen v0.15.0 (/tmp/dotenv/dotenv_codegen) > Finished dev [unoptimized + debuginfo] target(s) in 9.93s > > Parent is shutting down, bye... > > So how is this "very difficult"? The steps are the same as when I clone a > Python upstream git repo and I get the message "ModuleNotFoundError: No module > named 'foo'" -- I just install python3-foo and it will work. Same here with > rust and the librust-foo-dev packages.
I do think it's "very difficult". You end up calculating dependency trees by hand, instead of an automatic program, like cargo, pip. How does it come for version satisfaction? For example a library version installed in system path conflicts the software you are developing. -- Shengjing Zhu