unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jason Rumney <jasonr@gnu.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: cschol2112@googlemail.com, 'Eli Zaretskii' <eliz@gnu.org>,
	emacs-devel@gnu.org, 'Mathias Dahl' <mathias.dahl@gmail.com>
Subject: Re: Emacs Windows barebin distribution
Date: Tue, 20 Nov 2012 21:58:15 +0800	[thread overview]
Message-ID: <878v9w4brc.fsf@gnu.org> (raw)
In-Reply-To: <551F5F9812F347C08746E86B58C59129@us.oracle.com> (Drew Adams's message of "Sun, 18 Nov 2012 07:50:28 -0800")

"Drew Adams" <drew.adams@oracle.com> writes:

> 3. Matthias's suggestion is the best approach, assuming it can be done.
> Certainly the number of users who actually download barebins is an even more
> accurate indication of the need than a user poll would be.

The barebins were only ever useful for the following uses:

  1. Installing over the top of a source distribution without
     downloading the full bin package which has a lot of duplication
     with the source package.  In the days of 33k6 modems, this made
     some sense, but today the value is less obvious.

  2. Redumping Emacs. This use was questionable, as normally if Emacs
     were to be redumped, the user would need to change PURESIZE as
     well, so they would need to recompile everything themselves anyway.

I think today, these files are downloaded more in confusion over which
files are required, than by any deliberate need.  So studying the server
logs might not be as useful as you think.




  parent reply	other threads:[~2012-11-20 13:58 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-15 14:28 Emacs Windows barebin distribution Christoph Scholtes
2012-04-15 16:18 ` Eli Zaretskii
2012-11-16 22:48   ` Dani Moncayo
2012-11-16 22:54     ` Dani Moncayo
2012-11-17  7:50     ` Eli Zaretskii
2012-11-17  8:27       ` Dani Moncayo
2012-11-17  8:56         ` Eli Zaretskii
2012-11-18 12:52   ` Mathias Dahl
2012-11-18 15:30     ` Eli Zaretskii
2012-11-18 15:50       ` Drew Adams
2012-11-18 16:20         ` Juanma Barranquero
2012-11-18 17:12           ` Eli Zaretskii
2012-11-18 17:37             ` Drew Adams
2012-11-18 17:55               ` Eli Zaretskii
2012-11-18 18:22                 ` Drew Adams
2012-11-18 19:00                   ` Eli Zaretskii
2012-11-18 17:22           ` Drew Adams
2012-11-18 17:29             ` Juanma Barranquero
2012-11-18 17:39               ` Drew Adams
2012-11-18 17:45                 ` Juanma Barranquero
2012-11-18 18:22                   ` Drew Adams
2012-11-19  4:02               ` Stephen J. Turnbull
2012-11-18 17:36             ` Eli Zaretskii
2012-11-20 13:58         ` Jason Rumney [this message]
2012-11-21  4:23           ` Stephen J. Turnbull
2012-11-18 19:56       ` Mathias Dahl
2012-11-18 20:22         ` Dani Moncayo
2012-11-18 20:45           ` Dani Moncayo
2012-11-18 21:28             ` Eli Zaretskii
2012-11-18 21:14         ` Eli Zaretskii
2012-04-15 16:43 ` Jambunathan K
2012-04-16  0:02   ` Drew Adams

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=878v9w4brc.fsf@gnu.org \
    --to=jasonr@gnu.org \
    --cc=cschol2112@googlemail.com \
    --cc=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=mathias.dahl@gmail.com \
    /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).