From: Tom Tromey <tromey@redhat.com>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: Chong Yidong <cyd@stupidchicken.com>,
emacs-devel@gnu.org, rms@gnu.org, spedrosa@gmail.com,
phil@hagelb.org
Subject: Re: Emacs Package Management
Date: Tue, 29 Sep 2009 13:41:40 -0600 [thread overview]
Message-ID: <m363b1a68b.fsf@fleche.redhat.com> (raw)
In-Reply-To: <jwvvdj1in63.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 29 Sep 2009 15:18:10 -0400")
Stefan> In order to move forward on this thing, here's what I'd like to have as
Stefan> a first step: the equivalent of `dpkg', i.e. an elisp package that can
Stefan> take a package (a tarball, most likely) and "install it", list the set
Stefan> of installed packages, uninstall a package.
package.el does all of these...
Stefan> An important feature for me is that this should be able to "install
Stefan> without making available"
... but not this.
Stefan> So basically, the installation process would distinguish the following
Stefan> steps:
Stefan> - install: may include byte-compiling and things like that
Stefan> - activate: eval the autoload declarations, adjust the load-path, ...
Stefan> - make available: setup the .emacs so that the package gets activated
Stefan> at startup.
package.el does this.
Stefan> Activation should be done by loading a single file. I.e. "make
Stefan> available" is nothing more than add a (load "/foo/bar/baz") in the
Stefan> .emacs.
It does this too, though only a single (package-initialize) is needed --
package.el handles activating all the packages that can be activated.
Stefan> This "dpkg"-equivalent may also want to do dependency checking, although
Stefan> this is not absolutely necessary for the first step.
Also done.
Also, package.el sets the info path when a package ships a dir file.
Tom
next prev parent reply other threads:[~2009-09-29 19:41 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-01 21:27 Emacs Package Management Stephen Eilert
2008-08-01 22:58 ` Tom Tromey
2008-08-01 23:14 ` Phil Hagelberg
2008-08-01 23:25 ` Lennart Borgman (gmail)
2008-08-02 0:13 ` Tom Tromey
2008-08-03 1:33 ` Richard M. Stallman
2008-08-03 18:03 ` Stefan Monnier
2008-08-04 15:33 ` Richard M. Stallman
2008-08-04 19:07 ` Stefan Monnier
2008-08-05 8:04 ` Richard M. Stallman
2008-08-05 13:09 ` Stephen Eilert
2008-08-05 14:39 ` Paul R
2008-08-06 3:35 ` Richard M. Stallman
2009-09-16 22:36 ` Stephen Eilert
2009-09-17 1:44 ` Tom Tromey
2009-09-17 13:43 ` Stefan Monnier
2009-09-17 14:26 ` Tom Tromey
2009-09-17 14:58 ` Eric M. Ludlam
2009-09-28 21:13 ` Phil Hagelberg
2009-09-28 21:48 ` Lennart Borgman
2009-09-28 21:54 ` Chong Yidong
2009-09-28 22:30 ` Phil Hagelberg
2009-09-29 11:31 ` Richard Stallman
2009-09-29 19:18 ` Stefan Monnier
2009-09-29 19:41 ` Tom Tromey [this message]
2009-09-30 1:20 ` Stefan Monnier
2009-09-30 2:07 ` Tom Tromey
2009-09-30 4:39 ` Stefan Monnier
2009-09-30 20:18 ` Tom Tromey
2009-10-01 5:01 ` Stefan Monnier
2008-08-02 1:58 ` Stephen Eilert
2008-08-02 3:36 ` Tom Tromey
2008-08-02 17:30 ` Richard M Stallman
2008-08-12 4:10 ` Thomas Lord
2009-09-12 22:38 ` Phil Hagelberg
2009-09-12 23:30 ` Eric M. Ludlam
2009-09-13 16:40 ` Richard Stallman
2009-09-14 9:07 ` joakim
2009-09-14 9:26 ` David Kastrup
2009-09-15 7:16 ` Richard Stallman
2009-09-15 8:30 ` Miles Bader
2009-09-15 18:15 ` Richard Stallman
2009-09-15 18:58 ` Tom Tromey
2009-09-15 22:08 ` Miles Bader
2009-09-16 15:16 ` Richard Stallman
2009-09-16 18:41 ` Stefan Monnier
2009-09-17 1:05 ` Geoff Gole
2009-09-17 19:50 ` Richard Stallman
2009-09-15 18:55 ` Tom Tromey
2009-09-17 6:37 ` Richard Stallman
2009-09-17 8:28 ` Tassilo Horn
2009-09-17 8:37 ` joakim
2009-09-17 8:48 ` Lennart Borgman
2009-09-17 9:31 ` Tassilo Horn
2009-09-17 10:43 ` Lennart Borgman
2009-09-17 11:50 ` Rupert Swarbrick
2009-09-19 2:40 ` Bob Rogers
2009-09-19 12:10 ` Rupert Swarbrick
2009-09-17 14:24 ` Tom Tromey
2009-09-17 19:22 ` Tassilo Horn
2009-09-17 15:04 ` Eric M. Ludlam
2009-09-17 13:46 ` Stefan Monnier
2009-09-17 14:21 ` Tom Tromey
2009-09-13 17:00 ` Eric Schulte
2008-08-02 14:46 ` Paul R
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=m363b1a68b.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
--cc=phil@hagelb.org \
--cc=rms@gnu.org \
--cc=spedrosa@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 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.