unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>,  Eli Zaretskii <eliz@gnu.org>,
	arash@gnu.org,  Stefan Kangas <stefankangas@gmail.com>,
	jb@jeremybryant.net,  Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: Re Re: Why not include all ELPA packages in an Emacs release?
Date: Thu, 30 May 2024 06:31:14 +0000	[thread overview]
Message-ID: <874jafx13h.fsf@posteo.net> (raw)
In-Reply-To: <CAO48Bk9H1BcOSnv1rnxEpezpmSHQgXGWSk4Db_Yn29sZ+FUiKQ@mail.gmail.com> (Pedro Andres Aranda Gutierrez's message of "Thu, 30 May 2024 08:16:42 +0200")

Pedro Andres Aranda Gutierrez <paaguti@gmail.com> writes:

>> >>> And while we're at it: There are sometimes requests for adding AUCTeX
>> to
>> >>> core.  Do you have an opinion about that?
>> >>
>> >>I don't mind.  But let's hear what others think.
>> >
>> > Well, AUCTeX was so feature-bloated that made me start using vanilla
>> Emacs
>> > and writing the things I really needed myself. So grateful it existed,
>> > because it made my elisp evolve :-)
>>
>> This sounds like a LaTeX/AUCTeX-specific issue.  IIUC, you prefer the
>> built-in latex-mode that AUCTeX supersedes, right?  Or what do you mean
>> by bloated?
>>
>
> Jup, that was a purely LaTeX issue. And yes, I didn't have time to learn
> all the specifics
> of AUCTeX and did some customisation + yasnippets to get my phD thesis
> written.
> At that time, a switch from MSWord/OpenOffice to LaTeX was churning all my
> free CPU cycles,
> because I had work and real life in parallel.

[...]

> WRT the package size, I wouldn't worry that much.  Even a large package
>> like AUCTeX is just under 10MB in my /elpa/ directory.  The mean package
>> side on ELPA is about 100-150KB.  Packages like Debian that don't
>> bundled .el sources (instead just using .elc) by default might be even
>> better off.
>>
>
> But just keep in mind that there are situations, where the platform must
> deploy
> Emacs on, might not be as relaxed WRT disk space... And it's not about a
> specific
> package, it's about a trickle of packages becoming a flood...

I can imagine that a distribution like Debian can choose to distribute
two package.  The regular Emacs, that would bundle the selected ELPA
packages and "emacs-minimal" that wouldn't (and perhaps even remove some
more, like games or some stuff like that).

>> My .2 cents
>>
>> --
>>         Philip Kaludercic on peregrine
>>
>
> Best, /PA

-- 
	Philip Kaludercic on peregrine



  reply	other threads:[~2024-05-30  6:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-29 16:31 Re Re: Why not include all ELPA packages in an Emacs release? Pedro Andres Aranda Gutierrez
2024-05-29 20:36 ` Philip Kaludercic
2024-05-30  6:16   ` Pedro Andres Aranda Gutierrez
2024-05-30  6:31     ` Philip Kaludercic [this message]
2024-05-30 10:36       ` Pedro Andres Aranda Gutierrez
2024-05-30 14:34     ` A small(er) Emacs (was: Why not include all ELPA packages in an Emacs release?) Stefan Monnier

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=874jafx13h.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=arash@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jb@jeremybryant.net \
    --cc=monnier@iro.umontreal.ca \
    --cc=paaguti@gmail.com \
    --cc=stefankangas@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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