From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com, cygwin-licensing@cygwin.com
Subject: Re: Contributing license information?
Date: Thu, 20 Oct 2011 07:39:00 -0000 [thread overview]
Message-ID: <20111020073807.GC23092@calimero.vinschen.de> (raw)
In-Reply-To: <4E9F9A2A.2060806@cisra.canon.com.au>
On Oct 20 14:48, Luke Kendall wrote:
> Corinna Vinschen wrote:
> >On Aug 19 11:09, Luke Kendall wrote:
> >>Soon, I will have prepared a list of the location of every license
> >>file in every Cygwin package. My motivation is to make it easy for
> >>people to find the license information, if they need it.
> >>
> >>(Preparing this information has required a lot of work on my part,
> >>so I would be happy if something could be done to make it easy to
> >>keep the information up to date as packages are added and modified.)
> >>
> >>What is the best way to contribute the license-location information
> >>so it can be integrated into Cygwin?
> >
> >Just create a new package for the distro which keeps the information
> >and maintain it. Somebody will have to keep the information up to date
> >anyway.
> >
> >
> >Corinna
> >
>
> Is usr/share/doc/common-licenses/ within the "base-files" package,
> supposed to be the place where all license information is collected?
> Should I just use that?
It's a good place for this, yes.
> I only today noticed
> http://www.cygwin.com/ml/cygwin-apps/2004-06/msg00275.html
>
> I believe usr/share/doc/common-licenses/ lists many licenses that
> are not used in the base-files package.
That was not the intention. The intention was to collect licenses
used by the sum of Cygwin distro packages.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2011-10-20 7:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-19 1:09 Luke Kendall
2011-08-19 12:04 ` Corinna Vinschen
2011-08-22 23:46 ` Luke Kendall
2011-10-20 3:49 ` Luke Kendall
2011-10-20 7:39 ` Corinna Vinschen [this message]
2011-10-20 7:49 ` Corinna Vinschen
2011-10-21 2:02 ` Luke Kendall
2011-10-21 8:59 ` Corinna Vinschen
2011-10-21 16:42 ` David Sastre
2011-10-21 17:36 ` Corinna Vinschen
2011-10-25 1:01 Luke Kendall
2011-10-25 13:51 ` Corinna Vinschen
2011-10-25 20:07 ` David Sastre
2011-10-31 5:27 ` Luke Kendall
2011-10-31 14:27 ` Christopher Faylor
2011-11-01 2:18 ` Luke Kendall
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=20111020073807.GC23092@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-licensing@cygwin.com \
--cc=cygwin@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).