From: Jaeme Sifat via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 68017@debbugs.gnu.org
Subject: bug#68017: cargo-build-system should propagate inputs and native-inputs of dependencies
Date: Mon, 25 Dec 2023 02:45:56 -0500 [thread overview]
Message-ID: <208f4c3c-76cf-4106-8c48-cad4261acb86@runbox.com> (raw)
In-Reply-To: <19fc6a13-c5fe-4061-9794-984f07c30fe7@gmail.com>
I'm a bit confused about what you exactly mean. Can you provide an
example? Programmatically, the build-system isn't supposed to be
reflected (package components of the build-system) in the inputs fields
of packages, Rust is no different.
> NB: This is my first time packaging rust, so I may be wrong about stuff.
The typical way of creating Rust crate definitions is to use `guix
import crate <package-name-on-crates.io>' to obtain a template
definition that you'd refine after building and testing the package. If
the crate is not hosted on crates.io, then you would have to read the
`Cargo.toml' file for build instructions. The guix import command also
has a '--recursive' option to automate that process for all the
dependencies of a crate as well. It's a repetitive process for sure, but
you don't have to find out dependencies by build errors.
--
Jaeme
next prev parent reply other threads:[~2023-12-28 18:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-24 22:09 bug#68017: cargo-build-system should propagate inputs and native-inputs of dependencies Mikhail Tsykalov
2023-12-25 7:45 ` Jaeme Sifat via Bug reports for GNU Guix [this message]
2023-12-25 8:21 ` bug#68017: Clarification on why cargo-build-system should propagate inputs and native-inputs Mikhail Tsykalov
2023-12-25 20:02 ` Jaeme Sifat via Bug reports for GNU Guix
2023-12-27 10:43 ` Efraim Flashner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=208f4c3c-76cf-4106-8c48-cad4261acb86@runbox.com \
--to=bug-guix@gnu.org \
--cc=68017@debbugs.gnu.org \
--cc=jaeme@runbox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.