On 12/16/2013 07:29 PM, Robbie Gemmell wrote:
On 16 December 2013 18:54, Alan Conway <acon...@redhat.com> wrote:
The following are processed by various programs, I don't know if there's a
safe comment syntax. Can we get an exemption for such files?
QPID_VERSION.txt
cpp/QPID_VERSION.txt
The above seem reasonable as they contain only a version number. The below
I would guess depends on what is in them and how they are used, none of
which I have any knowledge of I'm afraid.
cpp/src/qpid.linkmap
The linker script can apparently take C-style comments (/* xyz */).
Though its tiny, it does contain build instructions.
cpp/src/qmf2.pc.in
cpp/src/qpid.pc.in
pkg conf files themselves can take comments in the form of lines
starting with '#' and I'm pretty sure the processing of these templates
by cmake won't be affected by the comments either. Not sure there would
be any strong argument that these required a license, but it may be
simpler to just add it.
cpp/src/tests/.valgrind.supp
cpp/src/tests/test.xquery
cpp/src/tests/legacystore/.valgrind.supp
cpp/src/tests/legacystore/.valgrindrc
I don't think the valgrind stuff requires a license (not sure if there
can be any comments i them). Its just suppressions to stop noise when
running, and some configuration to show up leaks. Nothing that I think
could credibly argued represents any creative work.
The test.xquery is in a file just for convenience in one of the tests
(to avoid extra quoting). Personally I don't think it needs a license
and its been there for a long time now anyway. If there was a strong
case put forward that it did need a license then the test script could
be modified to strip it out I'm sure. As I say though, for me this would
be rather pointless.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
