unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Jonathan Scoresby <me@jonscoresby.com>
To: "(" <paren@disroot.org>, help-guix@gnu.org
Subject: Re: Rust Packaging without crates.io
Date: Wed, 24 Aug 2022 10:23:52 -0600 (MDT)	[thread overview]
Message-ID: <2099203680.635993.1661358232923@office.mailbox.org> (raw)
In-Reply-To: <CMEDZ3HYHE3M.2Y1KKEJU3OQ7S@guix-aspire>


> On 08/24/2022 10:06 MDT ( <paren@disroot.org> wrote:
> 
>  
> Hi Jonathon,
> 
> You can just write a normal package for a crate on Git, replacing the source with
> something like:
> 
>   (origin
>     (method git-fetch)
>     (uri (git-reference
>           (url "...")
>           (commit (string-append "v" version))))
>     (file-name (git-file-name name version))
>     (sha256
>      (base32
>       "...")))
> 
> You can use a Rust package built like this in the same way as a normal crates.io
> crate. Just add it to cargo-inputs or cargo-development-inputs as appropriate :)
> 
>     -- (


Thank you for the reply. This is what I have done. The problem I am having is that when I do this, cargo is not referencing it properly. The Cargo.toml file will have a line like:

package = {git=url, rev=commit}

I have successfully packaged the package it is referencing in the fashion you have shown and have provided it under cargo-inputs, but cargo is still trying to find the package at the git url.

-Jonathan


  reply	other threads:[~2022-08-24 16:24 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 [this message]
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
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=2099203680.635993.1661358232923@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).