From: Csepp <raingloom@riseup.net>
To: Matthew James Kraai <kraai@ftbfs.org>
Cc: help-guix@gnu.org
Subject: Re: Build particular Rust version
Date: Sun, 28 Aug 2022 13:54:45 +0200 [thread overview]
Message-ID: <87h71wr364.fsf@riseup.net> (raw)
In-Reply-To: <YwqEZs9GgWHguT/4@carlo>
Matthew James Kraai <kraai@ftbfs.org> writes:
> Hi,
>
> Is it possible to build Rust 1.58.1 without updating the `rust`
> definition? If so, how do I do so?
>
> If I apply this patch:
>
> ```
> diff --git a/gnu/packages/rust.scm b/gnu/packages/rust.scm
> index 67dc5cdaf3..61d6686b64 100644
> --- a/gnu/packages/rust.scm
> +++ b/gnu/packages/rust.scm
> @@ -644,10 +644,14 @@ (define rust-1.56
> rust-1.55 "1.56.1" "04cmqx7nn63hzz7z27b2b0dj2qx18rck9ifvip43s6dampx8v2f3"))
>
> (define rust-1.57
> + (rust-bootstrapped-package
> + rust-1.56 "1.57.0" "06jw8ka2p3kls8p0gd4p0chhhb1ia1mlvj96zn78n7qvp71zjiim"))
> +
> +(define rust-1.58
> (let ((base-rust
> (rust-bootstrapped-package
> - rust-1.56 "1.57.0"
> - "06jw8ka2p3kls8p0gd4p0chhhb1ia1mlvj96zn78n7qvp71zjiim")))
> + rust-1.57 "1.58.1"
> + "1iq7kj16qfpkx8gvw50d8rf7glbm6s0pj2y1qkrz7mi56vfsyfd8")))
> (package
> (inherit base-rust)
> (outputs (cons "rustfmt" (package-outputs base-rust)))
> ```
>
> and run `./pre-inst-env guix build rust@1.58.1`, it outputs
>
> ```
> guix build: error: rust: package not found for version 1.58.1
> ```
I haven't tried building Rust, but at a glance it seems like the new
package inherits its version field from base-rust.
Guix doesn't really care what symbol you assign the package to, only the
version field matters. You could write (define-public
this-is-definitely-php rust-base) and it would still show up in `guix
search rust`.
prev parent reply other threads:[~2022-08-28 11:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-27 20:53 Build particular Rust version Matthew James Kraai
2022-08-28 11:54 ` Csepp [this message]
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=87h71wr364.fsf@riseup.net \
--to=raingloom@riseup.net \
--cc=help-guix@gnu.org \
--cc=kraai@ftbfs.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.
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.