From: Stephen Leake <stephen_leake@stephe-leake.org>
To: emacs-devel@gnu.org
Subject: Re: Local ELPA
Date: Tue, 24 Dec 2013 16:58:28 -0600 [thread overview]
Message-ID: <85lhz9ua97.fsf@stephe-leake.org> (raw)
In-Reply-To: <jwvha9y4a91.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 24 Dec 2013 09:05:36 -0500")
Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
>> - after ruthlessly deleting failing packages, and adding -Q, it
>> succeeds, but does not produce packages/archive-contents, so the
>> following fails:
>> (setq package-archives (list (cons "test" "/Projects/elpa/packages")))
>
> While there's some left-over ode that might support building such
> a local archive, I have no intention to support this mode of operation.
>
> Instead the recommended setup is a local *installation* of all GNU
> ELPA packages.
I don't understand what you mean by *installation*.
The reason I want a local ELPA archive is precisely to test that M-x
list-packages followed by install does the right thing with my package
under development.
If I want to install another package from ELPA in ~/.emacs.d, I'll use
the web access to ELPA.
You seem to be saying I should just create the .elc files in the git
workspace, and point to that in my .emacs, bypassing the 'package'
mechanisms; I don't see how that is useful.
--
-- Stephe
next prev parent reply other threads:[~2013-12-24 22:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-23 4:37 Local ELPA Daniel Colascione
2013-12-23 13:45 ` Stefan Monnier
2013-12-23 13:59 ` Stephen Leake
2013-12-23 16:05 ` Stefan Monnier
2013-12-24 8:57 ` Stephen Leake
2013-12-24 9:22 ` Stephen Leake
2013-12-24 14:07 ` Stefan Monnier
2013-12-24 22:58 ` Stephen Leake
2013-12-24 14:05 ` Stefan Monnier
2013-12-24 22:58 ` Stephen Leake [this message]
2013-12-25 16:27 ` Stefan Monnier
2013-12-23 14:56 ` Ted Zlatanov
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=85lhz9ua97.fsf@stephe-leake.org \
--to=stephen_leake@stephe-leake.org \
--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.