From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: gcovr - Suitable for Cygwin?
Date: Mon, 06 Jun 2016 19:18:00 -0000 [thread overview]
Message-ID: <20160606191840.GH4919@calimero.vinschen.de> (raw)
In-Reply-To: <20160606084958.GE14744@calimero.vinschen.de>
[-- Attachment #1: Type: text/plain, Size: 1163 bytes --]
On Jun 6 10:49, Corinna Vinschen wrote:
> On Jun 4 19:10, David Stacey wrote:
> > I've been using gcovr to generate coverage reports, and I'd be happy to
> > maintain this for Cygwin. Before submitting a package, I'd be grateful if
> > someone could check the licence [1].
> >
> > It's a fairly standard 3-clause BSD affair, but with the caveat that 'the
> > U.S. Government retains certain rights in this software.' It isn't clear (to
> > me, at least) what rights are being referred to. Would such a clause
> > prohibit its inclusion in Cygwin?
> >
> > Note that gcovr isn't available for Fedora or CentOS, although this could be
> > because it hasn't been packaged for these distros, rather than any
> > incompatibility in the licence. It is, however, available for Debian and
> > Ubuntu [2].
> >
> > Any thoughts on its suitability for Cygwin?
>
> Let me ask somebody who knows this better than me...
Ok, nothing to worry about. Please go ahead if you like.
Thanks,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-06-06 19:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-04 18:10 David Stacey
2016-06-06 8:50 ` Corinna Vinschen
2016-06-06 19:18 ` Corinna Vinschen [this message]
2016-06-06 21:14 ` David Stacey
2016-06-06 12:15 ` Achim Gratz
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=20160606191840.GH4919@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-apps@cygwin.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).