From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Barry <gundaetiapo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs release and bundling GNU Elpa
Date: Wed, 24 Jun 2015 10:04:16 -0400 [thread overview]
Message-ID: <jwva8vpxlnk.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <F6F3868E-0A04-45CE-B02F-302F753ACCF1@yahoo.com> (Barry's message of "Wed, 24 Jun 2015 01:12:16 -0700")
>> step-3: we change the build scripts again so they always use those
>> packages from elpa.git.
> What are the essential reasons for having two Git repos rather than one?
If you look beyond actual repositories (which are just arbitrary
containers of data), there are more than 2 branches: there's the
emacs.git branch "master", the elpa.git branch "master", and the various
other elpa.git branches of the form "externals/<pkg>".
We want ELPA packages to live their own life, to be released at their
own pace.
> Is the vision that core Emacs could eventually be reduced to the Elisp
> engine and other infrastructure, and ELPA constitutes the features?
No.
>> I think the net result will be more bugs because of unsynchronized
>> development and less exposure of packages to people who track
>> development on master
Yes, there will be more total bugs, simply because the Emacs tarball will
be bigger. But as long as those "bundled ELPA packages" (BEPs) don't
affect other bundled packages, it's not worse than if the user
had to install those packages by hand.
So all it takes to keep those extra bugs under control is to check the
autoloads of those BEPs.
Stefan
next prev parent reply other threads:[~2015-06-24 14:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-24 8:12 Emacs release and bundling GNU Elpa Barry
2015-06-24 14:04 ` Stefan Monnier [this message]
2015-06-24 15:01 ` Eli Zaretskii
2015-06-24 15:44 ` Phillip Lord
-- strict thread matches above, loose matches on Subject: below --
2015-06-21 9:59 Artur Malabarba
2015-06-22 0:45 ` Stefan Monnier
2015-06-22 11:20 ` Phillip Lord
2015-06-22 13:27 ` Artur Malabarba
2015-06-22 13:30 ` Artur Malabarba
2015-06-22 13:30 ` Artur Malabarba
2015-06-22 15:22 ` Phillip Lord
2015-06-22 15:33 ` Stefan Monnier
2015-06-22 15:33 ` Eli Zaretskii
2015-06-22 16:50 ` Stephen Leake
2015-06-22 17:16 ` Stefan Monnier
2015-06-22 17:45 ` Artur Malabarba
2015-06-22 18:49 ` Eli Zaretskii
2015-06-23 10:55 ` Artur Malabarba
2015-06-23 13:20 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwva8vpxlnk.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=gundaetiapo@yahoo.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.