From: phillip.lord@russet.org.uk (Phillip Lord)
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Emacs 26.1 on Windows is HUGE
Date: Fri, 26 Apr 2019 21:59:08 +0100 [thread overview]
Message-ID: <874l6kh49v.fsf@russet.org.uk> (raw)
In-Reply-To: <83sgu4wszs.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 26 Apr 2019 20:56:07 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: phillip.lord@russet.org.uk (Phillip Lord)
>> Date: Fri, 26 Apr 2019 17:22:45 +0100
>> Cc: Óscar Fuentes <ofv@wanadoo.es>, help-gnu-emacs@gnu.org,
>> Björn Lindqvist <bjourne@gmail.com>
>>
>> Well, I was curious enough to look it up -- it's librsvg which has three
>> python scripts as part of it. Whether it actually uses them or not I
>> don't know. And, it is this that brings in lots of other things,
>> including, for example, bzip2.
>
> 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?
Phil
next prev parent reply other threads:[~2019-04-26 20:59 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 [this message]
2019-04-26 21:29 ` Óscar Fuentes
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874l6kh49v.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.