From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Luis Felipe <luis.felipe.la@protonmail.com>
Cc: Sunshine <sunshine@uberspace.net>, guix-devel@gnu.org
Subject: Re: Permanent URL for GUIX packages
Date: Fri, 4 Nov 2022 23:16:11 +0100 [thread overview]
Message-ID: <20221104221611.ciljpp6wmzkyp5sv@thebird.nl> (raw)
In-Reply-To: <Byg64VKTJUKc3xu-UI3wbvbFs0v3FCt4QNyHFydKxDQyc7mTmp0cY3bQPRXXOrZInDKT9mMsQpWWkFHzSIwlzebiVmCCmfjUiyyLPzPWr-s=@protonmail.com>
On Fri, Nov 04, 2022 at 03:49:15PM +0000, Luis Felipe via Development of GNU Guix and the GNU System distribution. wrote:
> > I'd like to link guix.gnu.org/packages/monolith-2.6.1/ from my project's README file (https://github.com/Y2Z/monolith), but due to the version string being part of the URL, I can't easily do that, would have to change the link for every new release.
>
> Right, the current paths are not that useful.
Indeed. A page giving installation instruction would be useful the way
Conda does it:
https://anaconda.org/bioconda/vcflib
It invites the user to try.
Pj.
next prev parent reply other threads:[~2022-11-04 22:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 15:50 Permanent URL for GUIX packages Sunshine via Development of GNU Guix and the GNU System distribution.
2022-11-04 13:21 ` pelzflorian (Florian Pelz)
2022-11-04 14:04 ` Sunshine via Development of GNU Guix and the GNU System distribution.
2022-11-04 15:49 ` Luis Felipe via Development of GNU Guix and the GNU System distribution.
2022-11-04 19:45 ` Sunshine via Development of GNU Guix and the GNU System distribution.
2022-11-04 22:16 ` Pjotr Prins [this message]
2022-11-05 12:07 ` zimoun
2022-11-05 14:33 ` Sunshine via Development of GNU Guix and the GNU System distribution.
2022-11-19 16:35 ` Luis Felipe via Development of GNU Guix and the GNU System distribution.
2022-11-22 18:24 ` Sunshine via Development of GNU Guix and the GNU System distribution.
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=20221104221611.ciljpp6wmzkyp5sv@thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=guix-devel@gnu.org \
--cc=luis.felipe.la@protonmail.com \
--cc=sunshine@uberspace.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 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.