From: Eli Zaretskii <eliz@gnu.org>
To: Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Bloat in Windows (revisited)
Date: Mon, 10 Jun 2019 18:27:45 +0300 [thread overview]
Message-ID: <83a7epbgum.fsf@gnu.org> (raw)
In-Reply-To: <2bd8b71e-cf67-32d0-7457-ecd6e5d05adc@gmail.com> (message from Nikolay Kudryavtsev on Mon, 10 Jun 2019 11:52:55 +0300)
> From: Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
> Date: Mon, 10 Jun 2019 11:52:55 +0300
>
> I was wondering about this bloat too. So the gist of my question is - do we have to bundle dependencies with
> their optional stuff due to some reason, like licensing requirements?
No, the only reason is that "Someone" has to figure out which parts
are necessary for Emacs and which aren't. Assuming, that is, that no
one will use these binary distributions for any purpose other than
running Emacs.
next prev parent reply other threads:[~2019-06-10 15:27 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 21:46 Bloat in Windows (revisited) Phillip Lord
2019-06-05 23:24 ` Tak Kunihiro
2019-06-06 14:29 ` Eli Zaretskii
2019-06-06 14:34 ` Stefan Monnier
2019-06-06 20:14 ` Phillip Lord
2019-06-07 2:07 ` Stefan Monnier
2019-06-09 21:16 ` Phillip Lord
2019-06-10 8:59 ` Nikolay Kudryavtsev
2019-06-10 12:17 ` Óscar Fuentes
2019-06-10 15:47 ` Nikolay Kudryavtsev
2019-06-10 21:28 ` Phillip Lord
2019-06-13 17:27 ` Nikolay Kudryavtsev
2019-06-13 17:53 ` Eli Zaretskii
2019-06-13 18:12 ` Nikolay Kudryavtsev
2019-06-13 21:34 ` Phillip Lord
2019-06-14 8:19 ` Nikolay Kudryavtsev
2019-06-17 15:59 ` Phillip Lord
2019-06-18 16:29 ` Eli Zaretskii
2019-06-18 17:59 ` Stefan Monnier
2019-06-18 19:27 ` Óscar Fuentes
2019-06-13 21:31 ` Phillip Lord
2019-06-07 6:08 ` Eli Zaretskii
2019-06-10 8:52 ` Nikolay Kudryavtsev
2019-06-10 15:27 ` Eli Zaretskii [this message]
2019-06-10 21:17 ` Phillip Lord
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=83a7epbgum.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=nikolay.kudryavtsev@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 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.