From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: emacs-devel@gnu.org
Subject: Re: ELPA -- making individual packages
Date: Thu, 03 Sep 2020 21:08:45 -0400 [thread overview]
Message-ID: <jwvv9gugxo1.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87363yjue9.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Thu, 03 Sep 2020 16:46:38 -0700")
> 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.
[ Hmm... cpio-mode seems to build fine for me (with a crapload of
warnings, tho). Can you send me the error log so I can try and
fix it? ]
> 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 don't think `make` can do exactly that, but there's no doubt that we
should be able to provide a way to build just a particular package
(maybe the target would have to be called something else than just
`gnorb`, e.g. `compile-gnorb`). It's probably not that hard.
Stefan
next prev parent reply other threads:[~2020-09-04 1:08 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
2020-09-04 1:11 ` Stefan Kangas
2020-09-04 1:08 ` Stefan Monnier [this message]
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=jwvv9gugxo1.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=eric@ericabrahamsen.net \
/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.