From: Eli Zaretskii <eliz@gnu.org>
To: phillip.lord@russet.org.uk (Phillip Lord)
Cc: arash.esbati@gmail.com, emacs-devel@gnu.org
Subject: Re: Emacs binaries for Windows
Date: Tue, 23 Aug 2016 17:35:56 +0300 [thread overview]
Message-ID: <83h9abft83.fsf@gnu.org> (raw)
In-Reply-To: <87lgzn4th3.fsf@russet.org.uk> (phillip.lord@russet.org.uk)
> From: phillip.lord@russet.org.uk (Phillip Lord)
> Cc: arash.esbati@gmail.com, emacs-devel@gnu.org
> Date: Tue, 23 Aug 2016 12:26:00 +0100
>
> >> emacs-*-bin.tar.gz -- as is now (with libnoX4)
> >> emacs-*-libraries.tar.gz -- with binaries for libraries
> >> emacs-*-libraries.sources.tar.gz -- with sources for the libraries
> >
> > No, I meant each library in a separate archive. Again, that's just my
> > opinion, something I do all the time on the ezwinports site.
>
> Would that not be a pain to install? You have to unpack them all
> separately? Irritating from the desktop.
Not sure why this would be a pain. Unpacking .tar.gz files is already
a pain on Windows (which is why ezwinports uses only *.zip files,
which can be unpacked with the Windows Explorer). But once that
obstacle has been negotiated, why does it matter whether one needs to
unpack one file or a dozen?
The advantage is that since the libraries don't have to change too
frequently, you can unpack them only once, and after that only install
the Emacs binary, leaving the libraries intact.
next prev parent reply other threads:[~2016-08-23 14:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-19 7:45 Emacs binaries for Windows Arash Esbati
2016-08-19 14:50 ` Eli Zaretskii
2016-08-19 16:33 ` Arash Esbati
2016-08-19 17:51 ` Eli Zaretskii
2016-08-19 20:27 ` Óscar Fuentes
2016-08-20 15:49 ` Arash Esbati
2016-08-20 15:58 ` Eli Zaretskii
2016-08-22 10:37 ` Phillip Lord
2016-08-22 14:54 ` Eli Zaretskii
2016-08-23 11:26 ` Phillip Lord
2016-08-23 14:35 ` Eli Zaretskii [this message]
2016-08-23 17:02 ` Arash Esbati
2016-08-23 17:21 ` Eli Zaretskii
2016-08-24 10:42 ` Phillip Lord
2016-08-19 15:03 ` Phillip Lord
2016-08-19 17:24 ` Arash Esbati
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=83h9abft83.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=arash.esbati@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=phillip.lord@russet.org.uk \
/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.