[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
a few questions on GNU ELPA
From: |
Ivan Shmakov |
Subject: |
a few questions on GNU ELPA |
Date: |
Thu, 29 Jan 2015 13:45:37 +0000 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) |
Reading elpa/README left me with a few unanswered questions.
First of all, – when the package is of the multi-file variety,
would the “release machinery” be somehow offended should
I import the pre-release history /without/ the respective
PKG/PKG.el file, – used (AIUI) for its Version: metadata field?
(I’ll then push that file in a separate “release” commit.)
Now, that same file is going to have a dozen lines of code
(excluding comments) at most (that is: mainly the ‘defgroup’ and
‘provide’ forms.) Should I use the GPL3+ notice for that file
(as the rest of the code uses), or would the simple
all-permissive license [1] be also acceptable?
Also regarding the release machinery, do I understand it
correctly that there’s currently no way to maintain several
(say, “development” and “stable”) branches in GNU ELPA?
TIA.
[1]
https://gnu.org/software/texinfo/manual/texinfo/html_node/All_002dpermissive-Copying-License.html
--
FSF associate member #7257 http://boycottsystemd.org/ … 3013 B6A0 230E 334A
- a few questions on GNU ELPA,
Ivan Shmakov <=