* [bug#38408] [PATCH] WIP patches for the rust importer
[not found] ` <785501a89e81d30db021047529e7262e@riseup.net>
@ 2019-12-04 2:40 ` Ivan Petkov
0 siblings, 0 replies; only message in thread
From: Ivan Petkov @ 2019-12-04 2:40 UTC (permalink / raw)
To: Martin Becze; +Cc: guix-devel, 38408, Efraim Flashner
[-- Attachment #1: Type: text/plain, Size: 1233 bytes --]
Hi Martin,
> On Dec 2, 2019, at 3:10 PM, Martin Becze <mjbecze@riseup.net> wrote:
>
> When you say source import of the transitive dependencies, do you mean
> that all the rust libs should just be source only or do you mean the top
> level package should have to declare all the transitive dependencies?
All rust libs should be source only imports, but each package definition
should only declare dependencies on the crates it consumes directly and
guix should figure out the rest (in other words, I’d expect there to be a
one-to-one mapping between a Cargo.toml and a package definition).
For example, if crate foo depends on crate bar which depends on crate
baz, I’d expect the definitions to look like:
(define-public rust-foo
(package
(name “rust-foo")
(source-input `((“bar” ,bar)))))
(define-public rust-bar
(package
(name “rust-bar")
(source-input `((“baz” ,baz)))))
(define-public rust-baz
(package
(name “rust-baz")))
But while building foo (assuming it is some kind of application), guix
would ensure that bar and baz are available in the build environment.
IMO this direction would be the most maintainable in the long term.
—Ivan
[-- Attachment #2: Type: text/html, Size: 4585 bytes --]
^ permalink raw reply [flat|nested] only message in thread