unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Stefan Kangas <stefan@marxist.se>,  emacs-devel@gnu.org
Subject: Re: Replace 'pp' with 'prin1' to generate ELPA archive-contents
Date: Sat, 22 Oct 2022 15:05:59 +0000	[thread overview]
Message-ID: <87pmejsxt4.fsf@posteo.net> (raw)
In-Reply-To: <jwvczajx61i.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sat, 22 Oct 2022 11:00:55 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

> Stefan Kangas [2022-10-22 04:56:47] wrote:
>> Philip Kaludercic <philipk@posteo.net> writes:
>>> I've just tried replacing the 'pp' call with 'prin1' in elpa-admin's
>>> `elpaa-update-archive-contents', and on my checkout the size dropped
>>> from ~130 kb to 100 kb.  It is not much, but I don't understand why the
>>> archive contents should be pretty printed, and even a few kilobyte less
>>> can make a difference for some people.
>> If we care about 30kb, how adding gzip support instead?
>
> Gzippping this file and the tarballs would be a very welcome
> change, yes.  The main issue is to make sure all the expected clients
> can decompress those files.
>
> IOW we need to add support for that to `package.el`.
> The sooner the better.
>
> AFAIK it's pretty easy to add support to Apache to auto-generate the
> `.gz` files on the fly.  I tried setting up the server to do the
> opposite (automatically serving the uncompressed version of the file
> when the file name without `.gz` is requested) but couldn't get it
> to work.

I am not an Apache expert, but from what I read the "SetOutputFilter
DEFLATE" directive should enable gzip compression for requests where the
client supports it.



  reply	other threads:[~2022-10-22 15:05 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 [this message]
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=87pmejsxt4.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=stefan@marxist.se \
    /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).