unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Phillip Lord <phillip.lord@russet.org.uk>
To: "Juan José García-Ripoll" <juanjose.garciaripoll@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Avoid duplicate emacs.exe / emacs-$version.exe
Date: Sun, 29 Mar 2020 14:08:34 +0100	[thread overview]
Message-ID: <87tv27b965.fsf@russet.org.uk> (raw)
In-Reply-To: <86ftdrxzzz.fsf@csic.es> ("Juan José García-Ripoll"'s message of "Sun, 29 Mar 2020 11:38:08 +0200")

Juan José García-Ripoll <juanjose.garciaripoll@gmail.com> writes:

> Eli Zaretskii <eliz@gnu.org> writes:
>>> Just a side note: the build-zips.sh script that makes the Windows
>>> distribution files always uses the flag -static when building emacs.
>> I don't think the build should use that.  It is certainly not the
>> default.
>
> So where is the default? Is the default build process not the one in
> emacs/admin/nt or, in case one builds from sources without creating zip
> files, the one in emacs/nt/? I am reporting data from running those two
> procedures. If you are claiming I am not doing the standard thing, where
> is the standard thing?
>
> Apologies if I may sometimes sound rude, but I am committing my workflow
> and part of my group's to Emacs for various reasons (org-mode, latex, ebib,
> etc) and I would like to contribute make the upcoming releases work
> nicely with our systems.


It's fine to critique things, but we also need fixes that are
better. The hard link ain't got to work in a zip. But hard-linking is
right for the other situations, so changing the build (i.e. make) to fix
this isn't probably not a good idea. So, we have a minor problem, with
no obvious solution. Again, I doubt that 6Mb is a problem for anyone; is
it causing you any difficulties?

If you are really raring to make Emacs work nicely with other systems,
then the two main problems with the windows build at the moment are the
lack of an MSI, and a mechanism for signing the binaries so they don't
produce a warning on running.

Phil



  reply	other threads:[~2020-03-29 13:08 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-28 16:53 Avoid duplicate emacs.exe / emacs-$version.exe Juan José García-Ripoll
2020-03-28 18:19 ` Eli Zaretskii
2020-03-28 20:41   ` Juan José García-Ripoll
2020-03-28 22:45     ` Phillip Lord
2020-03-29  2:31     ` Eli Zaretskii
2020-03-29  9:38       ` Juan José García-Ripoll
2020-03-29 13:08         ` Phillip Lord [this message]
2020-03-29 14:10         ` Eli Zaretskii
2020-03-28 18:19 ` Eli Zaretskii
2020-03-28 20:13   ` Phillip Lord
2020-03-28 20:48     ` Juan José García-Ripoll
2020-03-28 22:22       ` Phillip Lord
2020-03-28 23:36         ` Juan José García-Ripoll
2020-03-29 12:55           ` Phillip Lord
2020-03-29  2:27     ` Eli Zaretskii
2020-03-29 12:52       ` Phillip Lord
2020-03-29 13:56         ` Eli Zaretskii
2020-03-29 17:25           ` Phillip Lord
2020-03-28 23:36   ` Juan José García-Ripoll
2020-03-29  2:36     ` Eli Zaretskii
2020-03-29 12:59       ` Phillip Lord
2020-03-29 13:59         ` Eli Zaretskii
2020-03-29 18:18           ` Phillip Lord
2020-03-29 18:34             ` Eli Zaretskii
2020-03-29 20:49               ` Phillip Lord
  -- strict thread matches above, loose matches on Subject: below --
2020-03-29 17:01 Angelo Graziosi
2020-03-29 17:22 ` 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=87tv27b965.fsf@russet.org.uk \
    --to=phillip.lord@russet.org.uk \
    --cc=emacs-devel@gnu.org \
    --cc=juanjose.garciaripoll@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).