unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Óscar Fuentes" <ofv@wanadoo.es>
To: phillip.lord@russet.org.uk (Phillip Lord)
Cc: help-gnu-emacs@gnu.org
Subject: Re: Emacs 26.1 on Windows is HUGE
Date: Fri, 26 Apr 2019 23:29:38 +0200	[thread overview]
Message-ID: <874l6k1mm5.fsf@telefonica.net> (raw)
In-Reply-To: <874l6kh49v.fsf@russet.org.uk> (Phillip Lord's message of "Fri, 26 Apr 2019 21:59:08 +0100")

phillip.lord@russet.org.uk (Phillip Lord) writes:

>> Maybe report that to the MSYS2 packagers.  It's IMO wrong to consider
>> every package that comes with a few Python script not essential to its
>> functionality to be dependent on Python.
>
> Hmmm. Actually, it's indirect, via libglib2.
>
> The dependency was added deliberately in this commit.
>
> d394f202ab275d931f9408c68a4dc1fa95ad723c
>
> viewable here:
>
> https://github.com/msys2/MINGW-packages/commit/d394f202ab275d931f9408c68a4dc1fa95ad723c#diff-4edc48d8f1e38f841d1aa74999389b6e
>
> A priori, I am a bit surprised this is a runtime rather than build time
> dependency, or possibly the dependency on python should be in
> gobject-introspection only. Adding a python dependency to glib seems
> quite a blunt solution. But my knowledge in this is limited to say the
> least. What do think, Eli? Worth reporting?

On that URL an user asked about the dependency on python, no response.

MSYS2 is strongly influenced by Archlinux. Although MSYS2 is quite
sloppy about dependencies (among other things) Archlinux is a differente
beast, and on its PKGBUILD (1) for glib2 python is listed on
`makedepends' and `optdepends', not on `depends'. For me, that warrants
a report. Better, create a PR moving python to `makedepends' and
`optdepends' and CC the author of the commit you referred to on the PR
message.

But... don't expect that MSYS2 makes changes to adapt to your specific
needs. Creating an stand-alone distribution of Emacs is not the same as
managing packages in MSYS2. For instance: as you know, lib* packages in
MSYS2 comes with binaries + development files (.a & *.h ...) while
distributing those with Emacs is dubious. You already remove them from
your zipfiles, why don't do the same with python? BTW, since MSYS2 is
sloppy with dependencies, you can't rely on them for making sure that
everything is included.

And on different topic, did you test that C-h i works as it should? Does
it show the Emacs info files? There is a long-standing problem with
Emacs on MSYS2 about this, although IIRC only happens when you install
Emacs as an MSYS2 package. But since testing it only takes a few
seconds... (I can't test myself, computer attracted lightning)


1 https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/glib2



  reply	other threads:[~2019-04-26 21:29 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-14 22:01 Emacs 26.1 on Windows is HUGE Björn Lindqvist
2019-04-15  1:40 ` Óscar Fuentes
2019-04-15 11:42   ` Phillip Lord
2019-04-15 14:55     ` Óscar Fuentes
2019-04-15 17:00       ` Phillip Lord
2019-04-16 20:57     ` Björn Lindqvist
2019-04-16 21:19       ` Phillip Lord
2019-04-16 22:18         ` Björn Lindqvist
2019-04-17  2:48           ` Eli Zaretskii
2019-04-17  3:34             ` Óscar Fuentes
2019-04-17  4:13               ` Eli Zaretskii
2019-04-17 15:28             ` Phillip Lord
2019-04-17 16:41               ` Eli Zaretskii
2019-04-19  8:13           ` Tomas Nordin
2019-04-23 15:11             ` Phillip Lord
2019-04-25 19:54               ` Tomas Nordin
2019-04-26 16:22                 ` Phillip Lord
2019-04-26 17:56                   ` Eli Zaretskii
2019-04-26 20:59                     ` Phillip Lord
2019-04-26 21:29                       ` Óscar Fuentes [this message]
2019-04-27 11:17                         ` Phillip Lord
2019-04-27 11:26                           ` Eli Zaretskii
2019-04-29 13:55                             ` Phillip Lord
2019-04-29 15:12                               ` Eli Zaretskii
2019-04-30  9:48                                 ` Phillip Lord
2019-04-30 15:09                                   ` Eli Zaretskii
2019-04-30 15:35                                     ` Óscar Fuentes
2019-04-30 16:05                                       ` Eli Zaretskii
2019-04-30 21:13                                         ` Phillip Lord
2019-05-01  2:43                                           ` Eli Zaretskii
2019-05-01  4:04                                             ` Eli Zaretskii
2019-05-01 14:22                                               ` INFOPATH on MSYS(2) (WAS: Emacs 26.1 on Windows is HUGE) Noam Postavsky
2019-05-01 17:17                                                 ` Eli Zaretskii
2019-05-01 22:07                                                 ` INFOPATH on MSYS(2) Phillip Lord
2019-05-02  2:36                                                   ` Eli Zaretskii
     [not found]                                         ` <87pnopx929.fsf@russet.org.uk>
2019-05-11 16:14                                           ` Emacs 26.1 on Windows is HUGE Phillip Lord
2019-05-13 13:27                                             ` Óscar Fuentes
2019-04-27  7:14                       ` Eli Zaretskii
2019-04-16 20:35   ` Björn Lindqvist
2019-04-16 20:54     ` Óscar Fuentes
2019-04-17  4:09       ` Björn Lindqvist
2019-04-17 15:25         ` Óscar Fuentes
2019-04-17 16:36           ` 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=874l6k1mm5.fsf@telefonica.net \
    --to=ofv@wanadoo.es \
    --cc=help-gnu-emacs@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.
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).