[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [nongnu] elpa/rainbow-delimiters a32b39bdfe: Add license file with G
From: |
Philip Kaludercic |
Subject: |
Re: [nongnu] elpa/rainbow-delimiters a32b39bdfe: Add license file with GPLv3 |
Date: |
Mon, 03 Jan 2022 08:20:03 +0000 |
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
- Re: [nongnu] elpa/rainbow-delimiters a32b39bdfe: Add license file with GPLv3, Stefan Monnier, 2022/01/01
- Re: [nongnu] elpa/rainbow-delimiters a32b39bdfe: Add license file with GPLv3, Stefan Kangas, 2022/01/01
- Re: [nongnu] elpa/rainbow-delimiters a32b39bdfe: Add license file with GPLv3, Stefan Kangas, 2022/01/01
- Re: [nongnu] elpa/rainbow-delimiters a32b39bdfe: Add license file with GPLv3, Philip Kaludercic, 2022/01/02
- Re: [nongnu] elpa/rainbow-delimiters a32b39bdfe: Add license file with GPLv3, Stefan Kangas, 2022/01/02
- Re: [nongnu] elpa/rainbow-delimiters a32b39bdfe: Add license file with GPLv3, Stefan Monnier, 2022/01/02
- Re: [nongnu] elpa/rainbow-delimiters a32b39bdfe: Add license file with GPLv3, Stefan Kangas, 2022/01/03
- Re: [nongnu] elpa/rainbow-delimiters a32b39bdfe: Add license file with GPLv3, Stefan Monnier, 2022/01/03
- Re: [nongnu] elpa/rainbow-delimiters a32b39bdfe: Add license file with GPLv3, Richard Stallman, 2022/01/02
- Re: [nongnu] elpa/rainbow-delimiters a32b39bdfe: Add license file with GPLv3,
Philip Kaludercic <=
- Re: [nongnu] elpa/rainbow-delimiters a32b39bdfe: Add license file with GPLv3, Richard Stallman, 2022/01/03
- Re: [nongnu] elpa/rainbow-delimiters a32b39bdfe: Add license file with GPLv3, Stefan Monnier, 2022/01/02
- Re: [nongnu] elpa/rainbow-delimiters a32b39bdfe: Add license file with GPLv3, Stefan Kangas, 2022/01/02
- Re: [nongnu] elpa/rainbow-delimiters a32b39bdfe: Add license file with GPLv3, Stefan Monnier, 2022/01/02
- Re: [nongnu] elpa/rainbow-delimiters a32b39bdfe: Add license file with GPLv3, Stefan Kangas, 2022/01/03
- Re: [nongnu] elpa/rainbow-delimiters a32b39bdfe: Add license file with GPLv3, Stefan Monnier, 2022/01/04
Re: [nongnu] elpa/rainbow-delimiters a32b39bdfe: Add license file with GPLv3, Stefan Monnier, 2022/01/01