unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Arash Esbati <arash.esbati+ml@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, Phillip Lord <phillip.lord@russet.org.uk>
Subject: Re: Emacs binaries for Windows
Date: Tue, 23 Aug 2016 19:02:52 +0200	[thread overview]
Message-ID: <86mvk31kqr.fsf@gmail.com> (raw)
In-Reply-To: <83h9abft83.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 23 Aug 2016 17:35:56 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> 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?

I think another issue would be making every single archive
self-contained then.  The way I understand it many (all?) DLLs rely on
`libgcc_s_seh-1.dll'.  So this one must be packed in every archive.  I
think your ezwinports are built this way.

For the start, I think I go with Phil: Pack the DLLs into one archive
and tell users to unpack them into the directory where emacs.exe resides
and be done with it.  This procedure can be changed later, if necessary.

Just my 2 cents.

Best, Arash



  reply	other threads:[~2016-08-23 17:02 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
2016-08-23 17:02                   ` Arash Esbati [this message]
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

  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=86mvk31kqr.fsf@gmail.com \
    --to=arash.esbati+ml@gmail.com \
    --cc=eliz@gnu.org \
    --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 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).