From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Nicolas P. Rougier (inria)" <nicolas.rougier@inria.fr>
Cc: emacs-devel@gnu.org
Subject: Re: ELPA: New package: svg-lib
Date: Mon, 27 Sep 2021 17:02:02 -0400 [thread overview]
Message-ID: <jwvpmstpwna.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <m18rzh3fsg.fsf@inria.fr> (Nicolas P. Rougier's message of "Mon, 27 Sep 2021 22:47:05 +0200")
> Thanks for the report. I've fixed most of them and let you know when
> everythign is fixed.
I see you fixed the copyright which is the only one that mattered, so
I pushed it, thanks. Should appear in GNU ELPA as soon as you bump the
`Version:` header (the commit which introduced the `Version: 1.0` still
had problematic copyright info, which will prevent building that
tarball).
> May I ask how you get such detailed report on the byte compilation?
The spurious "Required package ‘<foobar>’ is unavailable" were
graciously provided by some bugs in my config, the likes of "refs to
free var" and the "unused var" should come from `make packages/svg-lib`
(which basically compiles each file in a fresh Emacs session in batch
mode), and some others come from local hacks I have in my personal
branch of Emacs.
Stefan
next prev parent reply other threads:[~2021-09-27 21:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 13:49 ELPA: New package: svg-lib Nicolas P. Rougier (inria)
2021-09-27 14:34 ` Stefan Kangas
2021-09-27 14:34 ` Stefan Kangas
2021-09-27 17:38 ` Alan Third
2021-09-27 18:03 ` Nicolas P. Rougier (inria)
2021-09-27 20:19 ` Alan Third
2021-09-27 20:43 ` Nicolas P. Rougier (inria)
2021-09-27 20:03 ` Stefan Monnier
2021-09-27 20:47 ` Nicolas P. Rougier (inria)
2021-09-27 20:59 ` Stefan Kangas
2021-09-28 5:32 ` Nicolas P. Rougier (inria)
2021-09-27 21:02 ` Stefan Monnier [this message]
2021-09-28 5:34 ` Nicolas P. Rougier (inria)
2021-09-28 4:29 ` Adam Porter
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=jwvpmstpwna.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=nicolas.rougier@inria.fr \
/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.