From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: help-gnu-emacs@gnu.org
Subject: Re: Elpa packages and Makefiles
Date: Sun, 13 Jul 2014 09:39:49 +0800 [thread overview]
Message-ID: <87mwceujdm.fsf@ericabrahamsen.net> (raw)
In-Reply-To: CAAjq1me0o1uAqC57C9CjpBZi4rxcHOYYgqU=LwnQbEsN0rjykQ@mail.gmail.com
Grant Rettke <gcr@wisdomandwonder.com> writes:
> To think through the process and decide how you would package it up
> yourself, try setting
> up an el-get recipe: https://github.com/dimitri/el-get
>
> Once you've got that thought through, you will be able to get any
> package maintainer whatever they need to package up your software
> because you will know precisely what steps you wanted to be performed.
Thanks, Grant. In this case, I *am* the package maintainer, and I know
what I want, I just don't know how Elpa interacts with Makefiles...
> Grant Rettke | ACM, ASA, FSF, IEEE, SIAM
> gcr@wisdomandwonder.com | http://www.wisdomandwonder.com/
> “Wisdom begins in wonder.” --Socrates
> ((λ (x) (x x)) (λ (x) (x x)))
> “Life has become immeasurably better since I have been forced to stop
> taking it seriously.” --Thompson
>
>
> On Fri, Jul 11, 2014 at 10:26 PM, Eric Abrahamsen
> <eric@ericabrahamsen.net> wrote:
>> I'm slowly working on a getting a package Elpa-ready, and have just a
>> few more questions. One is the role of a Makefile.
>>
>> The only targets I really need are compilation, autoloads, and texinfo.
>> My understanding is that Elpa deployment will do all these things for me
>> (the last dependent on the presence of "<package>.texi" and "dir"
>> files). I don't need a Makefile for that.
>>
>> But I would like to also make the package installable straight from
>> github or other locations, in which case a Makefile will still be
>> necessary.
>>
>> In the Elpa repo I've seen packages with Makefiles, with no Makefiles,
>> and even with Makefiles that contain an "elpa" target. My question is,
>> 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.
>>
>> Thanks!
>> E
>>
>>
next prev parent reply other threads:[~2014-07-13 1:39 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 [this message]
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
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=87mwceujdm.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.