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 11:11:30 -0600 (MDT) [thread overview]
Message-ID: <982283759.638640.1661361090785@office.mailbox.org> (raw)
In-Reply-To: <CMEFAHA2TOBE.VXWQ86P21422@guix-aspire>
> On 08/24/2022 11:08 MDT ( <paren@disroot.org> wrote:
>
> You could add a version constraint to it if you like; what's the version
> in the dependency's cargo.toml?
It's rev={commit}
-Jonathan
next prev parent reply other threads:[~2022-08-24 17:14 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
2022-08-24 17:08 ` (
2022-08-24 17:11 ` Jonathan Scoresby [this message]
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=982283759.638640.1661361090785@office.mailbox.org \
--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).