emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Eli Zaretskii
Subject: Re: [feature/dll-only-windows] A new windows build, comments wanted
Date: Mon, 11 Jan 2021 17:21:43 +0200

> From: Phillip Lord <phillip.lord@russet.org.uk>
> Cc: emacs-devel@gnu.org
> Date: Mon, 11 Jan 2021 09:59:29 +0000
> 
> > 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.

Not necessarily: on platforms other than MS-Windows, if Emacs was
linked against some optional library, that library must be installed
for Emacs to run without crashing.

So on MS-Windows you could build Emacs with all the possible
extensions, and let users decide which ones they want to install and
use.

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

Did we reach any conclusions?

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

We stop where you decide to stop.  (And the utility of aspell is much
smaller than that of gzip, btw.  And the complexity of aspell
installation is OTOH significantly greater.)  There's no need for any
consistency here.  "Consistency is the hobgoblin", and all that.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]