From: Chong Yidong <cyd@stupidchicken.com>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: emacs-devel@gnu.org
Subject: Re: Keeping an ELPA checkout
Date: Fri, 25 Mar 2011 17:06:38 -0400 [thread overview]
Message-ID: <87sjuavrj5.fsf@stupidchicken.com> (raw)
In-Reply-To: <87fwqaudjs.fsf@lifelogs.com> (Ted Zlatanov's message of "Fri, 25 Mar 2011 15:53:59 -0500")
Ted Zlatanov <tzz@lifelogs.com> writes:
> But ELPA packages are... packages! Everything in emacs/lisp is source
> code, meant to work as you describe. Some ELPA packages happen to be
> single-file libraries but you are trying to skip the installation and
> activation steps which track dependencies, byte-compile, and adjust the
> load path.
Currently, we only have a script for deploying the elpa branch to an
archive, i.e. to a place from which the packages can be installed.
With a bit more work, we could add another script (or a Makefile rule)
for *installing* all the packages in the archive to a given location (or
even in place). By pointing `package-directory-list' to that directory,
one would have all the packages in the archive installed in one step.
This is probably what Stefan has in mind.
next prev parent reply other threads:[~2011-03-25 21:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 22:21 Keeping an ELPA checkout Stefan Monnier
2011-03-25 8:19 ` Reiner Steib
2011-03-25 21:09 ` Stefan Monnier
2011-03-25 14:46 ` Ted Zlatanov
2011-03-25 19:52 ` Stefan Monnier
2011-03-25 20:53 ` Ted Zlatanov
2011-03-25 21:06 ` Chong Yidong [this message]
2011-03-25 21:16 ` Ted Zlatanov
2011-03-26 19:31 ` Tom Tromey
2011-03-25 21:12 ` Stefan Monnier
2011-03-25 22:02 ` Ted Zlatanov
2011-03-25 23:20 ` Stefan Monnier
2011-03-28 18:38 ` Ted Zlatanov
2011-03-29 1:16 ` Stefan Monnier
2011-03-29 15:06 ` Ted Zlatanov
2011-03-29 21:16 ` Stefan Monnier
2011-03-30 13:28 ` Ted Zlatanov
2011-03-30 21:29 ` Stefan Monnier
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=87sjuavrj5.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=tzz@lifelogs.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).