From: Jonathan Scoresby <me@jonscoresby.com>
To: "(" <paren@disroot.org>
Cc: help-guix@gnu.org
Subject: Re: Rust Packaging without crates.io
Date: Wed, 24 Aug 2022 17:05:41 +0000 (UTC) [thread overview]
Message-ID: <27eaf18a-f99a-4c48-9819-493cc40275e3@jonscoresby.com> (raw)
In-Reply-To: <CMEF13CSLO05.20MZIW3LGBX93@guix-aspire>
I mean that the referenced package could be anything. I feel like guix should somehow verify that the referenced package was built from the source specified in the cargo.toml.
Also, it does not check the version. If the main package changed to depend on a newer version, the suggested more of creating a package definition would allow one to build the new package using the outdated dependency.
Anywhere I can read about antioxidant?
-Jonathan
next prev parent reply other threads:[~2022-08-24 17:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 1:38 Rust Packaging without crates.io Jonathan Scoresby
2022-08-24 16:06 ` (
2022-08-24 16:23 ` Jonathan Scoresby
2022-08-24 16:29 ` (
2022-08-24 16:52 ` Jonathan Scoresby
2022-08-24 16:56 ` (
2022-08-24 17:05 ` Jonathan Scoresby [this message]
2022-08-24 17:08 ` (
2022-08-24 17:11 ` Jonathan Scoresby
2022-08-24 17:12 ` (
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=27eaf18a-f99a-4c48-9819-493cc40275e3@jonscoresby.com \
--to=me@jonscoresby.com \
--cc=help-guix@gnu.org \
--cc=paren@disroot.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).