From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-devel@gnu.org
Subject: Re: ELPA -- making individual packages
Date: Thu, 03 Sep 2020 17:36:55 -0700 [thread overview]
Message-ID: <87y2lqidi0.fsf@ericabrahamsen.net> (raw)
In-Reply-To: CADwFkmkRZpYG5wpGc=LfWb4pg3xsLuPO7t3No2i5Ovi8A43kdg@mail.gmail.com
Stefan Kangas <stefankangas@gmail.com> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> I just realized to my horror that my Gnorb package in ELPA barfs up
>> several screenfuls of warnings when it compiles. I'd like to fix those
>> warnings by compiling it with a clean batch Emacs, using the GNUmakefile
>> in the git repo, but my only option is to make *all* the packages at
>> once, and that fails almost immediately on cpio-mode.
>>
>> Can "make" do catchall targets, where for instance I could say "make
>> gnorb" and make would check that "gnorb" isn't an existing target, and
>> the catchall target would say "if the directory "packages/gnorb" exists
>> then compile that, otherwise bail"?
>>
>> I'm guessing the answer is no...
>
> AFAIK, the answer is indeed no.
>
> This has also been discussed in Bug#38140:
>
> https://debbugs.gnu.org/38140
Ah, I missed that, thanks. Well, if it's not something that can be done
cleanly using existing "make" functionality, I don't think it's worth
hacking anything together. It's always possible to put something
together on the command line.
Thanks,
Eric
next prev parent reply other threads:[~2020-09-04 0:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 23:46 ELPA -- making individual packages Eric Abrahamsen
2020-09-04 0:18 ` Stefan Kangas
2020-09-04 0:36 ` Eric Abrahamsen [this message]
2020-09-04 1:11 ` Stefan Kangas
2020-09-04 1:08 ` Stefan Monnier
2020-09-04 3:25 ` Eric Abrahamsen
2020-09-08 13:12 ` Stefan Monnier
2020-09-08 16:19 ` Eric Abrahamsen
2020-09-08 17:07 ` Eric Abrahamsen
2020-09-04 13:01 ` Benjamin Riefenstahl
2020-09-04 17:41 ` Eric Abrahamsen
2020-09-04 22:20 ` Eric Abrahamsen
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=87y2lqidi0.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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.