unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: Mauricio Collares <mauricio@collares.org>
Cc: 46441@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#46441: GNU ELPA feature request: host .lz archives (as well as uncompressed) for current versions
Date: Fri, 12 Feb 2021 17:32:23 +0000	[thread overview]
Message-ID: <87ft21qjiw.fsf@tcd.ie> (raw)
In-Reply-To: <87r1lml74t.fsf@collares.org> (Mauricio Collares's message of "Thu, 11 Feb 2021 16:46:42 -0300")

[CCing the GNU ELPA maintainer.]

Mauricio Collares <mauricio@collares.org> writes:

> Currently, there's no way to get a permanent link to a package version
> that happens to be the current one. For example, auctex is currently at
> version 13.0.4; today I can download it from
> https://elpa.gnu.org/packages/auctex-13.0.4.tar, but this link will stop
> working as soon as a new version of auctex is released and the old
> version gets compressed. This makes it slightly annoying to pin a
> particular version of an ELPA package by URL.
>
> I would like to ask the GNU ELPA maintainers to host both
> https://elpa.gnu.org/packages/PACKAGE-CURRENTVERSION.lz (permanent) as
> well as https://elpa.gnu.org/packagesa/PACKAGE-CURRENTVERSION
> (temporary). This would make it easier for people to build reproducible
> environments by pinning a package version. I don't particularly care
> about exposing it as a link on the website; for my purposes, it's enough
> that the file exists. This is perhaps a little bit wasteful, but
> compressed versions shouldn't be too big.

Wouldn't it be wasteless if the "current version" URL was symbolic and
resolved to the concrete versioned release?

Thanks,

-- 
Basil





  reply	other threads:[~2021-02-12 17:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-11 19:46 bug#46441: GNU ELPA feature request: host .lz archives (as well as uncompressed) for current versions Mauricio Collares
2021-02-12 17:32 ` Basil L. Contovounesios [this message]
2021-02-12 18:10   ` Stefan Monnier
2021-02-12 18:36     ` Mauricio Collares
2021-02-12 19:08       ` Basil L. Contovounesios
2021-02-12 19:31         ` Mauricio Collares
2021-02-12 22:26       ` Stefan Monnier
2021-04-04  1:00     ` Stefan Kangas
2021-04-04 23:09       ` Stefan Monnier
2021-02-12 18:41   ` Mauricio Collares

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://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ft21qjiw.fsf@tcd.ie \
    --to=contovob@tcd.ie \
    --cc=46441@debbugs.gnu.org \
    --cc=mauricio@collares.org \
    --cc=monnier@iro.umontreal.ca \
    /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/emacs.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).