From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Wiegley Subject: Re: Sync up the org in emacs master to org maint branch? Date: Thu, 02 Feb 2017 21:01:49 -0500 Message-ID: References: <87k29d7zvw.fsf@engster.org> <87efzk2xg8.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: In-Reply-To: <87efzk2xg8.fsf@gmail.com> (Edward John Steere's message of "Mon, 30 Jan 2017 20:51:19 +0200") List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sender: "Emacs-devel" To: Edward John Steere Cc: David Engster , Emacs developers , Bastien Guerry , emacs-org list , Kaushal Modi , Phillip Lord List-Id: emacs-orgmode.gnu.org >>>>> "EJS" == Edward John Steere writes: EJS> What I think that we shouldn't lose sight of (if I may suggest it): is EJS> that packaging CEDET, Org Mode and other packages like them in a process EJS> which integrates them only when producing the tarball would serve to EJS> simplify things for everyone. Emacs core wouldn't be able to depend on EJS> packages which are more relevant to the users (and package developers) of EJS> Emacs, but these packages would still there like they always have been EJS> when one downloads binary Emacs. This is the very point I was hoping to make, thanks Edward. If it can simplify things for everyone, great; if it really will only complicate things, not so great. Many software projects have package ecosystems surrounding them that deal with similar issues, and I can't, off-hand, think of cases where the answer was "let's move some of those packages into core development to ease ___". This is why I find it a bit surprising that some feel so strongly about keeping these large, external packages in core. -- John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2