From: Stefan Kangas <stefankangas@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>,
Philip Kaludercic <philipk@posteo.net>
Cc: emacs-devel@gnu.org
Subject: Re: Replace 'pp' with 'prin1' to generate ELPA archive-contents
Date: Wed, 26 Oct 2022 07:33:56 -0700 [thread overview]
Message-ID: <CADwFkmnEcpc1nW-Q6GQrtsw2tttq3NaoVtNVYoasp-HubQ02Ug@mail.gmail.com> (raw)
In-Reply-To: <jwv1qqux03w.fsf-monnier+emacs@gnu.org>
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> No, otherwise they'd be `.tar.gz`, `.tar.lz`, etc...
> We don't compress them so that you can install them even from Emacsen
> that don't have access to a `.gz` decompressor.
Could we provide both the .tar and .tar.gz, and leave it up to
package.el to download whichever one is supported?
Or do we have very limited disk space?
next prev parent reply other threads:[~2022-10-26 14:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-22 10:52 Replace 'pp' with 'prin1' to generate ELPA archive-contents Philip Kaludercic
2022-10-22 11:56 ` Stefan Kangas
2022-10-22 13:45 ` Philip Kaludercic
2022-10-22 15:01 ` Stefan Kangas
2022-10-22 15:33 ` Philip Kaludercic
2022-10-22 15:00 ` Stefan Monnier
2022-10-22 15:05 ` Philip Kaludercic
2022-10-25 19:28 ` Stefan Monnier
2022-10-26 6:43 ` Philip Kaludercic
2022-10-26 11:20 ` Eli Zaretskii
2022-10-26 11:39 ` Philip Kaludercic
2022-10-26 12:10 ` Stefan Monnier
2022-10-26 12:18 ` Eli Zaretskii
2022-10-26 14:11 ` Po Lu
2022-10-26 15:02 ` Stefan Monnier
2022-10-26 15:18 ` Robert Pluim
2022-10-26 15:25 ` Stefan Monnier
2022-10-26 15:31 ` Robert Pluim
2022-10-27 0:50 ` Po Lu
2022-10-27 8:33 ` Robert Pluim
2022-10-27 10:38 ` Po Lu
2022-10-27 11:40 ` Robert Pluim
2022-10-27 11:48 ` Po Lu
2022-10-27 0:49 ` Po Lu
2022-10-27 15:17 ` Stefan Monnier
2022-10-26 14:33 ` Stefan Kangas [this message]
2022-10-26 15:03 ` Stefan Monnier
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=CADwFkmnEcpc1nW-Q6GQrtsw2tttq3NaoVtNVYoasp-HubQ02Ug@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=philipk@posteo.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/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.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.