From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: John Wiegley <jwiegley@gmail.com>
Cc: emacs-devel@gnu.org
Subject: ELPA and core services
Date: Mon, 25 Jun 2012 13:39:27 +0900 [thread overview]
Message-ID: <87zk7s80ow.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <m27guw76t3.fsf_-_@gmail.com>
John Wiegley writes:
> Please, please no. I use lots of Emacsen on lots of machines, and only a few
> have my configuration copied over. Please don't turn unconfigured Emacsen
> into brain-dead zombies of little value.
That won't happen. XEmacs made the mistake of distributing core
XEmacs without the SUMO package, but Emacs doesn't need to make the
same mistake, and even if it did it would be easy to rectify once you
have a package system. (It's also not that big a mistake, as the
continued, if attenuated, existence of XEmacs shows.)
> Now, this I agree with completely. ELPA overrides is a great idea, and I
> think it could accelerate development -- as long as inter-package version
> dependencies are managed.
I doubt it will accelerate development by much. Managing the real
dependencies between separately maintained code bases (even if they're
in the same tree!) is what slows down development, not distributing
changes.
next prev parent reply other threads:[~2012-06-25 4:39 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m2hau86tfk.fsf@vulcan.local.i-did-not-set--mail-host-address--so-tickle-me>
[not found] ` <E1ShM8F-0006IY-L9@fencepost.gnu.org>
[not found] ` <m2txy51z1k.fsf@newartisans.com>
[not found] ` <E1ShiKM-0000Aa-5G@fencepost.gnu.org>
2012-06-21 21:23 ` async 1.0 John Wiegley
2012-06-22 7:00 ` Teemu Likonen
2012-06-22 10:54 ` John Wiegley
2012-06-22 12:39 ` Michael Albinus
2012-06-22 22:02 ` John Wiegley
2012-07-04 17:10 ` Samuel Bronson
2012-07-05 4:09 ` John Wiegley
2012-07-05 19:58 ` Samuel Bronson
[not found] ` <82d34r8ej9.fsf@gmail.com>
2012-06-22 21:50 ` John Wiegley
2012-06-23 1:44 ` Stefan Monnier
2012-06-23 3:00 ` Stefan Monnier
2012-06-23 16:26 ` Lennart Borgman
2012-06-23 21:08 ` John Wiegley
2012-06-23 21:28 ` Jeremiah Dodds
2012-06-23 21:50 ` Thierry Volpiatto
2012-06-24 15:02 ` Christopher Schmidt
2012-06-24 15:42 ` Bastien
2012-06-24 21:01 ` John Wiegley
2012-06-25 14:53 ` Christopher Schmidt
2012-06-25 23:54 ` John Wiegley
2012-06-24 21:12 ` ELPA and core services John Wiegley
2012-06-24 21:40 ` Lennart Borgman
2012-06-25 2:20 ` Stefan Monnier
2012-06-25 4:39 ` Stephen J. Turnbull [this message]
2012-06-25 6:01 ` Achim Gratz
2012-07-03 14:38 ` Tom Tromey
2013-01-22 19:13 ` Achim Gratz
2012-06-25 4:32 ` stdlib for Emacs? [was: async 1.0] Stephen J. Turnbull
2012-06-23 6:25 ` async 1.0 Stephen J. Turnbull
2012-06-23 21:05 ` John Wiegley
2012-07-01 8:16 ` Michael Sperber
2012-06-22 11:38 ` Richard Stallman
2012-06-22 21:39 ` John Wiegley
2012-06-22 23:02 ` Richard Stallman
2012-06-23 7:46 ` zwz
2012-06-23 20:49 ` Richard Stallman
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=87zk7s80ow.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=emacs-devel@gnu.org \
--cc=jwiegley@gmail.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).