From: Stefan Kangas <stefankangas@gmail.com>
To: Philip Kaludercic <philipk@posteo.net>
Cc: emacs-devel@gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: Replace 'pp' with 'prin1' to generate ELPA archive-contents
Date: Sat, 22 Oct 2022 08:01:37 -0700 [thread overview]
Message-ID: <CADwFkmnK2LCNu0EAD_9-D-4iP1ywU6gCZb-xe3TzkzGOfUaMjQ@mail.gmail.com> (raw)
In-Reply-To: <874jvwotur.fsf@posteo.net>
Philip Kaludercic <philipk@posteo.net> writes:
> I have tried out a few different compression algorithms on the archive
> contents generated with `prin1', and it seems that bz2 would give the
> best results -- though in the end there is just a difference of ±2kb:
The main benefit of using gzip is that it's more portable, as it's
almost always installed on any given system. Given the small file
sizes, that consideration is probably more important than the exact
compression ratio.
> Another thing I just thought of is that HTTP can serve gzip'ed
> content, but unless I am mistaken the elpa.gnu.org server doesn't make
> use of this capability, even though url.el appears to send the right
> header (Accept-Encoding: gzip). My guess would be that enabling this
> would improve the situation immediately more than any hacking on
> elpa-admin.el/package.el.
Makes sense. Did you check what melpa.org does about that, BTW?
next prev parent reply other threads:[~2022-10-22 15:01 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 [this message]
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
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
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=CADwFkmnK2LCNu0EAD_9-D-4iP1ywU6gCZb-xe3TzkzGOfUaMjQ@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 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).