From: Tom Tromey <tromey@redhat.com>
To: "Andreas Röhler" <andreas.roehler@online.de>
Cc: help-gnu-emacs@gnu.org, Michael Olson <mwolson@gnu.org>,
Richard Stallman <rms@gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: ediff in RCS
Date: Sun, 24 Jun 2007 10:39:40 -0600 [thread overview]
Message-ID: <m3r6o12to3.fsf@fleche.redhat.com> (raw)
In-Reply-To: <200706182210.23703.andreas.roehler@online.de> ("Andreas Röhler"'s message of "Mon\, 18 Jun 2007 22\:10\:22 +0200")
>>>>> "Andreas" == Andreas Röhler <andreas.roehler@online.de> writes:
Andreas> What about to have a joined repository for
Andreas> third-party-stuff in a VC-system. Maybe Git, SVN,
Andreas> whatever. Together with a joined discussion of bugs as
Andreas> it takes place with the core-files?
Andreas> This pertains too for repositories as emacs-lisp-list,
Andreas> Tom Tromeys ELPA and probably other collections I
Andreas> ignore.
FWIW I wasn't planning to set up any sort of version control system
for ELPA. I do want to move it to a hosting service like savannah
eventually, so that other people can help maintain it. I don't have a
firm plan for when this will happen, I suppose whenever ELPA seems
"popular enough". Anyway, source control seems like a bit too much
process for this, at least right now.
Andreas> The problem seems in so far serious, as core-emacs can't
Andreas> grow eternal bigger and bigger. Rather I conceive a
Andreas> future, were independent packages are loaded as needed
Andreas> into a quick and stable core.
Andreas> Today already you may run into serious trouble, if your
Andreas> work depends on third-party-stuff, which for some
Andreas> reasons is no longer or not properly maintained (the
Andreas> latter is more or less inevitable with one-person-acts,
Andreas> as we all are making errors every day).
Andreas> At the other side the vast amount of third-party-stuff
Andreas> is very important and part of the strength
Andreas> of Emacs itself.
FWIW I don't mind having a maximal Emacs including everything -- I
rather like it, actually. But at the same time Emacs has a very long
and irregular release cycle, and some sub-packages may benefit from
decoupling a bit.
As for maintaining dependencies -- ELPA can only help with the
mechanics of this. If a package becomes unmaintained, or forks into
incompatible versions, that is not really something ELPA is intended
to solve. There are other ways to solve this though: get code into
Emacs, or have a way to hand off maintainership from one person to the
next to ensure package integrity.
Tom
next prev parent reply other threads:[~2007-06-24 16:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2307.1182121306.32220.help-gnu-emacs@gnu.org>
2007-06-17 23:14 ` ediff in RCS Hadron
2007-06-18 0:38 ` Drew Adams
2007-06-18 9:00 ` Hadron
2007-06-18 20:10 ` Andreas Röhler
2007-06-24 16:39 ` Tom Tromey [this message]
[not found] <mailman.2312.1182127247.32220.help-gnu-emacs@gnu.org>
2007-06-18 17:33 ` don provan
2007-06-17 22:12 Hadron
2007-06-17 23:00 ` Drew Adams
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=m3r6o12to3.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=andreas.roehler@online.de \
--cc=help-gnu-emacs@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=mwolson@gnu.org \
--cc=rms@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.
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).