unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: Why aren't ELPA packages compressed?
Date: Tue, 05 May 2015 10:24:03 -0400	[thread overview]
Message-ID: <87fv7b9k70.fsf@lifelogs.com> (raw)
In-Reply-To: 21832.50724.538350.789451@a1i15.kph.uni-mainz.de

On Tue, 5 May 2015 15:31:16 +0200 Ulrich Mueller <ulm@gentoo.org> wrote: 

>>>>>> On Tue, 05 May 2015, Tom Tromey wrote:
>> When I wrote package.el, one goal was that installing a package
>> would not require any external tool. So, e.g., that is why I chose
>> tar archives and not some other format -- tar-mode.el can unpack
>> them without a helper.

>>> From NEWS I see that zlib was added in 24. So, that's the reason --
>> at the time it wasn't available. It sounds like it is optional,
>> though, which seems like a problem for users.

UM> As was previously remarked, gzip could be used if Emacs isn't linked
UM> against zlib. And I wonder if there are still any systems nowadays
UM> where neither gzip nor zlib isn't readily available.

Both compressed and uncompressed tarballs could be available, each with
a separate signature. Then package.el could just get the smallest one it
can handle locally (so stuff like bz2 could also work). The web server
would require no more than the original storage for each compression
method but the downloads would be far smaller and faster. And it's
backwards compatible.

Ted




  reply	other threads:[~2015-05-05 14:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-04 16:31 Why aren't ELPA packages compressed? Ulrich Mueller
2015-05-04 16:56 ` Ivan Shmakov
2015-05-04 19:11   ` Stefan Monnier
2015-05-04 19:30   ` Ted Zlatanov
2015-05-05 13:12 ` Tom Tromey
2015-05-05 13:31   ` Ulrich Mueller
2015-05-05 14:24     ` Ted Zlatanov [this message]
2015-05-05 15:13     ` Eli Zaretskii

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=87fv7b9k70.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=emacs-devel@gnu.org \
    /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).