all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Richard Sent <richard@freakingpenguin.com>
Cc: guix-devel@gnu.org
Subject: Re: Creating an unversioned rust-cargo symbol
Date: Mon, 11 Mar 2024 10:58:46 +0200	[thread overview]
Message-ID: <Ze7HxoUS_bKO-s-X@3900XT> (raw)
In-Reply-To: <87y1b2q4dv.fsf@freakingpenguin.com>

[-- Attachment #1: Type: text/plain, Size: 1863 bytes --]

On Thu, Feb 29, 2024 at 05:42:20PM -0500, Richard Sent wrote:
> Hi Guix,
> 
> There isn't an unversioned symbol for rust-cargo defined or exported by
> the (gnu packages crates-io) module. I think it would be best if an
> unversioned rust-cargo symbol was created that was equal to the highest
> rust-cargo release. (i.e. rust-cargo, not rust-cargo-0.76)
> 
> Alternatively, since (seemingly) only one rust-cargo package is present
> at a time, perhaps the version information could be removed outright and
> only an unversioned symbol used.
> 
> The alternative, (specification->package), does not work in all
> circumstances (primarily with -L) [1]. This would also make Scheme code
> that refers to rust-cargo cleaner, either not needing updating every new
> version when the symbol changes or removing potentially awkward
> (specification->package) calls.
> 
> I see that most/all of the symbols in crates-io are versioned. While
> from a user perspective it would be nice if there were more unversioned
> symbols, rust-cargo is /probably/ the one that needs it the most since
> it's so central to the ecosystem. I can also see why versioning every
> symbol might help with development given Rust's release schedule and
> bootstrapping chain.
> 
> This would follow the pattern of linux-libre.
> 
> Posting to guix-devel instead of bug-guix since I'm not entirely sure
> this is a bug or working as intended.
> 
> [1] https://lists.gnu.org/archive/html/guix-devel/2022-12/msg00310.html
> 

I've added a rust-cargo package in rust-apps.scm and a note in
crates-io.scm to remove it with the next rust-team merge.

-- 
Efraim Flashner   <efraim@flashner.co.il>   רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2024-03-11  8:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-29 22:42 Creating an unversioned rust-cargo symbol Richard Sent
2024-03-11  8:58 ` Efraim Flashner [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=Ze7HxoUS_bKO-s-X@3900XT \
    --to=efraim@flashner.co.il \
    --cc=guix-devel@gnu.org \
    --cc=richard@freakingpenguin.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.