From: "Ludovic Courtès" <ludo@gnu.org>
To: Meiyo Peng <meiyo@riseup.net>
Cc: 35741-done@debbugs.gnu.org
Subject: [bug#35741] [PATCH] gnu: Add libdbusmenu.
Date: Fri, 24 May 2019 17:29:26 +0200 [thread overview]
Message-ID: <87lfyvx44p.fsf@gnu.org> (raw)
In-Reply-To: <877eaix6z5.fsf@riseup.net> (Meiyo Peng's message of "Thu, 23 May 2019 10:03:26 +0800")
Hello,
Meiyo Peng <meiyo@riseup.net> skribis:
>>> + ;; The shebang of the generated test files should be patched before
>>> + ;; enabling tests.
>>> + "--disable-tests")
>>
>> It would be nice if you could follow up with a patch to run the tests.
>
> Will try.
Great.
> libdbusmenu-glib, libdbusmenu-gtk, and some files in tools are dual
> licensed under LGPLv2.1 and LGPLv3. The rest files are licensed under
> GPLv3. For example:
>
> #+begin_example
> https://bazaar.launchpad.net/~dbusmenu-team/libdbusmenu/trunk.16.10/view/head:/tests/json-loader.c
> https://bazaar.launchpad.net/~dbusmenu-team/libdbusmenu/trunk.16.10/view/head:/tools/dbusmenu-dumper.c
> #+end_example
>
> So we should clarify it further.
I’d argue that ‘license’ is about the license of what we install, so the
license of the tests or build scripts (say) doesn’t matter much, but
‘dbusmenu-dumper’ is presumably something we install. So I agree:
further clarification is welcome!
Thanks for explaining,
Ludo’.
next prev parent reply other threads:[~2019-05-24 15:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 4:51 [bug#35741] [PATCH] gnu: Add libdbusmenu Meiyo Peng
2019-05-20 21:24 ` bug#35741: " Ludovic Courtès
2019-05-23 2:03 ` [bug#35741] " Meiyo Peng
2019-05-24 15:29 ` Ludovic Courtès [this message]
2019-05-25 2:00 ` Meiyo Peng
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=87lfyvx44p.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=35741-done@debbugs.gnu.org \
--cc=meiyo@riseup.net \
/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/guix.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.