From: Philip Kaludercic <philipk@posteo.net>
To: Richard Stallman <rms@gnu.org>
Cc: stefan@marxist.se, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: [nongnu] elpa/rainbow-delimiters a32b39bdfe: Add license file with GPLv3
Date: Mon, 03 Jan 2022 08:20:03 +0000 [thread overview]
Message-ID: <875yr1qlho.fsf@posteo.net> (raw)
In-Reply-To: <E1n4F6X-0005OY-Bx@fencepost.gnu.org> (Richard Stallman's message of "Sun, 02 Jan 2022 23:37:53 -0500")
Richard Stallman <rms@gnu.org> writes:
> [[[ To any NSA and FBI agents reading my email: please consider ]]]
> [[[ whether defending the US Constitution against all enemies, ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>
> > And while we are at it, is there a reason not to add a MELPA-like
> > keyword to manually specify what files are part of a package? Whenever
> > a single repository is used to maintain multiple packages (like Magit or
> > Embark) there is always a long list of :ignored-files that have to be
> > duplicated for every package. Perhaps a more general version of
> > .elpaignore could be used to declare packages externally.
>
> Would you please post a self-contained description of what you propose
> we do? One that doesn't assume any knowledge of MELPA?
Currently, each package specification may have the form
("foo" :url "https://git.host/path/to/repo"
:ignored-files ("Makefile" "baz.el"))
("baz" :url "https://git.host/path/to/repo"
:ignored-files ("Makefile" "foo.el"))
where I assume that the repository consists of the files foo.el, baz.el
and Makefile, and you would want to distribute two separate packages.
What I was thinking of was to add a keyword like :files to explicitly
list what files are added to a package:
("foo" :url "https://git.host/path/to/repo"
:files ("foo.el"))
("baz" :url "https://git.host/path/to/repo"
:files ("baz.el"))
--
Philip Kaludercic
next prev parent reply other threads:[~2022-01-03 8:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <164107430330.17202.17260845381664886032@vcs2.savannah.gnu.org>
[not found] ` <20220101215824.BB13CC0DEC3@vcs2.savannah.gnu.org>
2022-01-01 23:03 ` [nongnu] elpa/rainbow-delimiters a32b39bdfe: Add license file with GPLv3 Stefan Monnier
2022-01-01 23:47 ` Stefan Kangas
2022-01-02 0:02 ` Stefan Kangas
2022-01-02 11:52 ` Philip Kaludercic
2022-01-02 16:00 ` Stefan Kangas
2022-01-02 20:12 ` Stefan Monnier
2022-01-03 8:41 ` Stefan Kangas
2022-01-03 15:46 ` Stefan Monnier
2022-01-03 4:37 ` Richard Stallman
2022-01-03 8:20 ` Philip Kaludercic [this message]
2022-01-04 3:09 ` Richard Stallman
2022-01-02 20:02 ` Stefan Monnier
2022-01-02 20:24 ` Stefan Kangas
2022-01-02 20:31 ` Stefan Monnier
2022-01-04 4:04 ` Stefan Kangas
2022-01-04 6:04 ` Stefan Monnier
2022-01-02 0:16 ` Stefan Monnier
2022-01-02 1:34 ` Stefan Kangas
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=875yr1qlho.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rms@gnu.org \
--cc=stefan@marxist.se \
/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.