From: zimoun <zimon.toutoune@gmail.com>
To: Christopher Baines <mail@cbaines.net>, 59578@debbugs.gnu.org
Subject: [bug#59578] [PATCH] gnu: Add guile-fibers-latest.
Date: Fri, 25 Nov 2022 20:07:39 +0100 [thread overview]
Message-ID: <87edtqua2s.fsf@gmail.com> (raw)
In-Reply-To: <20221125170108.25413-1-mail@cbaines.net>
Hi Chris,
On Fri, 25 Nov 2022 at 17:01, Christopher Baines <mail@cbaines.net> wrote:
> * gnu/packages/guile-xyz.scm (guile-fibers-latest): New variable.
From my understanding, the convention seems ’-next’ and not ’-latest’.
--8<---------------cut here---------------start------------->8---
45 candidates:
./gnu/packages/freedesktop.scm:1210:(define-public wayland-protocols-next
./gnu/packages/bioconductor.scm:13526:(define-public r-cistopic-next
[...]
./gnu/packages/emacs-xyz.scm:25239:(define-public emacs-spaceline-next
--8<---------------cut here---------------end--------------->8---
Although, 6 packages are using ’-latest’. :-)
--8<---------------cut here---------------start------------->8---
6 candidates:
./gnu/packages/guile-xyz.scm:1359:(define-public guile-email-latest
./gnu/packages/bioinformatics.scm:4161:(define-public java-htsjdk-latest
./gnu/packages/tls.scm:333:(define-public gnutls-latest
./gnu/packages/guile.scm:391:(define-public guile-3.0-latest
./gnu/packages/perl.scm:5493:(define-public perl-inc-latest
./gnu/packages/ruby.scm:5378:(define-public ruby-latest-ruby
--8<---------------cut here---------------end--------------->8---
Well, since this appears in the name, it appears to me better to have
the same convention; for discover-ability, for instance.
Cheers,
simon
next prev parent reply other threads:[~2022-11-28 12:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 17:01 [bug#59578] [PATCH] gnu: Add guile-fibers-latest Christopher Baines
2022-11-25 19:07 ` zimoun [this message]
2022-11-28 21:06 ` Ludovic Courtès
2022-12-06 11:30 ` bug#59578: " Christopher Baines
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=87edtqua2s.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=59578@debbugs.gnu.org \
--cc=mail@cbaines.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).