From: Simon Tournier <zimon.toutoune@gmail.com>
To: Maxime Devos <maximedevos@telenet.be>, Mekeor Melire <mekeor@posteo.de>
Cc: 67292@debbugs.gnu.org
Subject: bug#67292: emacs / emacs-transient collisions and bundling
Date: Tue, 28 Nov 2023 10:45:57 +0100 [thread overview]
Message-ID: <868r6igqi2.fsf@gmail.com> (raw)
In-Reply-To: <daacad7f-20f7-3781-1137-0f85731c88ea@telenet.be>
On Tue, 28 Nov 2023 at 02:47, Maxime Devos <maximedevos@telenet.be> wrote:
>> Once builtin, the code of a package distributed with GNU Emacs is
>> maintained by Emacs maintainers and fully part of GNU Emacs.
>
> Yes, and? How does being fully part of GNU Emacs and being maintained
> by Emacs maintainers make it any less bundling? There is more to
> development than maintenance.
Please read GNU Emacs documentation and how GNU Emacs is developed. I
have tried to do my best for pointing you some links. If these are not
enough, you should dig by your own. Maybe ask on emacs-devel mailing
list how the GNU Emacs development process works.
> If making emacs-mnimal more minimal is too complicated, don't do it
> then, just replace the bundled copy with an up-to-date (source) version,
> as I proposed previously.
This is *not* the GNU Emacs release model. GNU Emacs version X.Y *is*
all the exact same files as the ones stored in Savannah. If you want to
replace the file
/gnu/store/…-emacs-X.Y/share/emacs/X.Y/lisp/transient.el.gz by something
else, you need to package that exact file. Therefore, your proposal
would imply to have two packages:
+ emacs-transient-next following development of transient.el – this
development happens outside Savannah. Please note for other builtin
packages, this development happens inside the Emacs repository
located in Savannah.
+ emacs-transient providing the exact same version as the builtin one
tracked in the GNU Emacs release X.Y branch located in Savannah.
Again, transient.el is not bundled. It is a builtin package which means
it is fully part of GNU Emacs. Being developed outside Savannah does
not make it bundled.
Regards,
simon
next prev parent reply other threads:[~2023-11-28 11:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-19 22:44 bug#67292: emacs / emacs-transient collisions and bundling Maxime Devos
2023-11-20 10:22 ` Simon Tournier
2023-11-20 12:39 ` Maxime Devos
2023-11-20 12:42 ` Maxime Devos
2023-11-20 13:46 ` Simon Tournier
2023-11-21 18:01 ` Maxime Devos
2023-11-22 20:53 ` Simon Tournier
2023-11-28 1:47 ` Maxime Devos
2023-11-28 9:45 ` Simon Tournier [this message]
2023-11-28 11:15 ` Mekeor Melire
2023-11-23 14:17 ` Mekeor Melire
2023-11-28 0:58 ` Maxime Devos
2023-11-28 11:12 ` Mekeor Melire
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=868r6igqi2.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=67292@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
--cc=mekeor@posteo.de \
/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/guix.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.