From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: help-gnu-emacs@gnu.org
Subject: Re: Elpa packages and Makefiles
Date: Wed, 01 Oct 2014 18:11:35 +0800 [thread overview]
Message-ID: <87oatwrtew.fsf@ericabrahamsen.net> (raw)
In-Reply-To: jwvy4vqfxfw.fsf-monnier+gmane.emacs.help@gnu.org
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> will Elpa deployment honor an existing Makefile (in which case, which
>> targets are used?), ignore it, or conflict -- ie I should .elpaignore it
>> or something.
>
> package.el currently just ignores the Makefile.
> It also ignores the .texi files, by the way (sadly).
Okay I'm finally actually getting around to this, playing with a local
deployment to see how it works, and still have a few questions (just one
for now).
I've got this package in Github as well, so I'm leaving it there, and
moving local development to a subtree in elpa/packages.
I started out with putting all the lisp files under a lisp/ directory in
the main package directory (for reasons that now escape me). That
includes the main PACKAGE.el entry-point file. I'd prefer not to mess
with this, for the sake of existing users. Is there any sort of crutch I
can use to both allow Elpa to create its top-level PACKAGE-pkg.el file
(and put the lisp/ directory on the load path), and also not disturb
users who are running from Github and have manually put lisp/ into their
load path?
Perhaps, if the "crutch" is simple, I could put it in a separate "elpa"
branch that gets rebased on top of master, then push master to Github,
and elpa to Elpa?
Thanks,
Eric
next prev parent reply other threads:[~2014-10-01 10:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-12 3:26 Elpa packages and Makefiles Eric Abrahamsen
2014-07-12 14:55 ` Grant Rettke
2014-07-13 1:39 ` Eric Abrahamsen
2014-07-18 16:23 ` Stefan Monnier
2014-07-19 0:26 ` Michael Heerdegen
2014-07-19 1:24 ` Eric Abrahamsen
2014-10-01 10:11 ` Eric Abrahamsen [this message]
2014-10-01 13:29 ` Stefan Monnier
2014-10-01 14:50 ` Eli Zaretskii
2014-10-01 17:06 ` Eric Abrahamsen
2014-10-08 3:32 ` Eric Abrahamsen
2014-10-08 18:31 ` Stefan Monnier
[not found] ` <mailman.10760.1412793114.1147.help-gnu-emacs@gnu.org>
2014-10-09 13:24 ` Ted Zlatanov
2014-10-09 14:40 ` Stefan Monnier
[not found] ` <mailman.10797.1412865640.1147.help-gnu-emacs@gnu.org>
2014-10-09 15:40 ` 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=87oatwrtew.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=help-gnu-emacs@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.