From: Noboru Ota <me@nobiot.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: [ELPA] Submitting new package Org-remark
Date: Sun, 30 Jan 2022 10:37:52 +0100 [thread overview]
Message-ID: <86k0eh8sy7.fsf@nobiot.com> (raw)
In-Reply-To: <jwvilu22xur.fsf-monnier+emacs@gnu.org>
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> [ BTW, your package didn't build yet because of:
> ======== Building tarball
> archive-devel/org-remark-0.2.0.0.20220129.95541.tar... Problem
> with copyright notices: Missing copyright notice in
> org-remark/demo/custom-pens.el Build error for
Thank you, Stefan.
I see. I assumed `.elpaignore` would also get applied to copyright check
function, but I just learned that it is not the case.
I have a feeling that `elpa-admin.el' could have a patch so that it
would also use `.elpaignore' to filter out `.el' files to check copyright
assignment? Function `elpaa--copyright-files' looks at `:ignored-files'
spec but not `.elpaignore' like function `elpaa--make-one-tarball-1'
does.
> Any chance you'd be interested in improving `describe-package`?
Interested, yes. I will need some time to get round to it (I have another
request from you regarding `text-clone'; I have not forgotten about it).
If the time is not an issue, I will see what I can do. I have a big
life event coming in October this year and my mind is already being
consumed by it (Org-remark is last project hanging off from the last year). Of course, others can jump in and do what is suggested.
Thanks again.
Noboru
next prev parent reply other threads:[~2022-01-30 9:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 19:07 [ELPA] Submitting new package Org-remark Noboru Ota
2022-01-28 21:05 ` Stefan Monnier
2022-01-29 9:30 ` Noboru Ota
2022-01-29 22:26 ` Stefan Monnier
2022-01-30 9:37 ` Noboru Ota [this message]
2022-01-30 16:13 ` Stefan Monnier
2022-01-29 20:36 ` Uwe Brauer
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=86k0eh8sy7.fsf@nobiot.com \
--to=me@nobiot.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.