From: phillip.lord@russet.org.uk (Phillip Lord)
To: Roland Winkler <winkler@gnu.org>
Cc: Joshua Branson <jbranso@fastmail.com>,
Bozhidar Batsov <bozhidar@batsov.com>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: RFC: Adding BBDB to Emacs core
Date: Mon, 23 Apr 2018 13:57:24 +0100 [thread overview]
Message-ID: <87o9iajd1n.fsf@russet.org.uk> (raw)
In-Reply-To: <87vacqcy89.fsf@gnu.org> (Roland Winkler's message of "Mon, 16 Apr 2018 22:23:34 -0500")
Roland Winkler <winkler@gnu.org> writes:
> On Sun, Apr 15 2018, John Wiegley wrote:
>>>>>>> "BB" == Bozhidar Batsov <bozhidar@batsov.com> writes:
>>
>> BB> You can add my voice to "I'd rather just have in ELPA (and we
>> BB> should be moving more and more packages there).
>>
>> Same here. I really don't want to see BBDB moved into core. I do want
>> ELPA packages to become more "first class" than they are now, so that
>> the desire to add such packages to core would no longer have the same
>> appeal.
>
> A simple scheme could be a policy for naming development and release
> branches of packages in the ELPA git repository (beyond the current
> "externals" branches for individual ELPA packages), combined with tools
> that allow one to access one or the other version of a package.
>
> Or yet something different.
I think this going to be scary because packages are distributed across
multiple branches, so names would end up getting namespaced. I think
that MELPA has it right here -- packages should be in different repos,
master is trunk, last tag is release. This could be expanded to support
multiple releases if package.el supported multiple versions of Emacs.
Phil
next prev parent reply other threads:[~2018-04-23 12:57 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-14 5:54 RFC: Adding BBDB to Emacs core Thomas Fitzsimmons
2018-04-14 12:24 ` Joshua Branson
2018-04-14 22:06 ` Eric Abrahamsen
2018-04-14 22:46 ` Joshua Branson
2018-04-15 6:18 ` Bozhidar Batsov
2018-04-16 5:21 ` John Wiegley
2018-04-16 14:53 ` Thomas Fitzsimmons
2018-04-16 18:36 ` Stefan Monnier
2018-04-16 20:30 ` Eric Abrahamsen
2018-04-17 3:37 ` Thomas Fitzsimmons
2018-04-23 12:53 ` Phillip Lord
2018-04-23 13:21 ` Stefan Monnier
2018-04-23 16:21 ` Phillip Lord
2018-04-23 17:45 ` Stefan Monnier
2018-04-24 21:41 ` Phillip Lord
2018-04-24 22:31 ` Stefan Monnier
2018-04-25 0:42 ` Paul Eggert
2018-04-25 1:50 ` Stefan Monnier
2018-04-25 9:21 ` Phillip Lord
2018-04-25 12:02 ` Stefan Monnier
2018-04-25 16:31 ` Phillip Lord
2018-04-25 16:57 ` Stefan Monnier
2018-04-26 14:59 ` Phillip Lord
2018-04-25 9:19 ` Phillip Lord
2018-04-25 16:04 ` Radon Rosborough
2018-04-25 16:32 ` Phillip Lord
2018-04-25 16:55 ` Stefan Monnier
2018-04-25 20:16 ` Radon Rosborough
2018-04-26 15:02 ` Phillip Lord
2018-04-26 16:38 ` Stefan Monnier
2018-04-27 9:57 ` Phillip Lord
2018-04-27 13:32 ` Stefan Monnier
2018-04-17 3:23 ` Roland Winkler
2018-04-17 4:56 ` John Wiegley
2018-04-17 13:07 ` Stefan Monnier
2018-04-17 15:13 ` Roland Winkler
2018-04-18 23:11 ` Stephen Leake
2018-04-23 12:57 ` Phillip Lord [this message]
2018-04-23 13:26 ` Stefan Monnier
2018-04-23 15:29 ` Roland Winkler
2018-04-14 22:13 ` Thomas Fitzsimmons
2018-04-14 13:34 ` Glenn Morris
2018-04-14 17:10 ` Radon Rosborough
2018-04-14 17:38 ` Thomas Fitzsimmons
2018-04-15 21:20 ` Phillip Lord
2018-04-16 3:11 ` Michael Welsh Duggan
2018-04-16 12:30 ` Stefan Monnier
2018-04-16 17:09 ` Achim Gratz
2018-04-16 18:10 ` Eli Zaretskii
2018-04-16 18:14 ` Achim Gratz
2018-04-23 12:45 ` 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=87o9iajd1n.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=bozhidar@batsov.com \
--cc=emacs-devel@gnu.org \
--cc=jbranso@fastmail.com \
--cc=winkler@gnu.org \
/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.