Re: [feature/dll-only-windows] A new windows build, comments wanted

[Phillip Lord]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Phillip Lord <phillip.lord@russet.org.uk>
>> Date: Sun, 10 Jan 2021 18:23:06 +0000
>> Cc: emacs-devel@gnu.org
>> 
>> I'd like to keep the Windows package using the default options as far as
>> possible, mostly because I am lazy and because it means that the windows
>> package updates when ever the defaults do.
>
> It's your call.  I just envision many users to expect native-comp
> support and asking why isn't it there.

No, you misunderstand me. I would plan to make Emacs-28
--with-nativecomp. But if I am doing this for the windows build, it is
reasonable to assume that other packagers will be doing for their
builds. If all that is true, it would make sense to me for it to be the
default.



>
>> Currently, we have
>> 
>> --without-dbus --without-compress-install
>> 
>> The latter is so the documentation works without gzip. The latter is
>> because we don't normally have dbus available. I am not sure why either
>> of these needed (i.e. why they are not the default on windows).
>
> The gzip thing is again your call (having gzip in the package is no
> big deal, IMO).  Dbus is not really useful on MS-Windows, so IMO it
> makes no sense building with it.

We've been down this road before. I could add gzip and I am happy to
consider this. But what other tools do we add. What about aspell
(or equivalent), so we can spell check? Git so we can version? If I add
them, then we get more "out-of-the-box" behaviour. But where do we stop.

Actually, for both of those, I'd rather see Emacs depend on their
respective libraries. Magit is widely reported to be usuable on Windows;
libgit integration might work around this. Anyway, getting off-topic.

Phil