From: joakim@verona.se
To: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: Re: Package.el merged
Date: Thu, 17 Jun 2010 07:42:44 +0200 [thread overview]
Message-ID: <m3ljae2p0r.fsf@verona.se> (raw)
In-Reply-To: <874oh2z8kp.fsf@stupidchicken.com> (Chong Yidong's message of "Wed, 16 Jun 2010 22:39:18 -0400")
Chong Yidong <cyd@stupidchicken.com> writes:
> I have now added package.el, Tom Tromey's package system, to the trunk.
> It's been discussed on this list previously; to summarize, it provides a
> convenient way to download and install Emacs Lisp packages and have them
> loaded automatically at startup.
This is fantastic news! Emacs 24 sure is starting to look good!
> One change, relative to package.el 0.9, is that package-archive-base now
> points to elpa.gnu.org, a server that the FSF has graciously provided
> for our use. This is currently mostly empty, except for a couple of
> test packages. Let's concentrate on polishing the packaging system
> before worrying about populating it.
Ok, but getting packages in there is also a process that needs testing.
> Two defcustoms, `package-enable' and `package-load-list', allow the
> package system to be disabled, or for only specific packages to be
> loaded, or disabled, or "held" at fixed versions. The default setting
> is to load all installed packages automatically at startup, after
> reading the init file.
>
> Currently package.el is not in loadup.el; I am still unsure whether to
> add it, or use autoloads and juggle things so that it's not loaded
> unless the user installs a package.
>
> There is still a great deal of polish that can be added, such as menu
> bar integration and improvements to the *packages* buffer (currently not
> very user friendly IMO). Also, Stefan has requested a way to make the
> way packages are loaded during start-up more transparent, to encourage
> users to customize it; I have some ideas about how to accomodate this
> within the current system, and am working on them.
>
> Regardless, I think it is good to check the code into the trunk earlier
> than later, so here it is. Go ahead and poke at the system, find flaws,
> etc.
>
>
> Also: if anyone among the active Emacs contributors is willing to help
> flesh out the elpa.gnu.org website, please email me!
--
Joakim Verona
next prev parent reply other threads:[~2010-06-17 5:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-17 2:39 Package.el merged Chong Yidong
2010-06-17 5:42 ` joakim [this message]
[not found] ` <AANLkTikn6YWhPHTSz9FqGgpkOLdYoTnfeWNIlhoxm9DP@mail.gmail.com>
2010-06-18 4:21 ` Fwd: " Phil Hagelberg
2010-06-18 16:30 ` Chong Yidong
2010-06-18 16:59 ` Juanma Barranquero
2010-07-19 19:36 ` Phil Hagelberg
2010-07-22 18:58 ` Chong Yidong
2010-07-28 18:57 ` Chong Yidong
2010-08-13 18:26 ` Ted Zlatanov
2010-08-14 15:01 ` package.el support for file: URLs (was: Package.el merged) Ted Zlatanov
2010-08-14 22:13 ` package.el support for file: URLs Chong Yidong
2010-08-15 2:11 ` Tom Tromey
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=m3ljae2p0r.fsf@verona.se \
--to=joakim@verona.se \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@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.