X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-0.6 required=5.0	tests=AWL,BAYES_20
X-Spam-Check-By: sourceware.org
Message-ID: <4E4DB7AC.7070702@cisra.canon.com.au>
Date: Fri, 19 Aug 2011 11:09:00 +1000
From: Luke Kendall <luke DOT kendall AT cisra DOT canon DOT com DOT au>
User-Agent: Thunderbird 2.0.0.21 (X11/20090302)
MIME-Version: 1.0
To: <cygwin AT cygwin DOT com>
CC: <audit-mail-disclaimer AT cisra DOT canon DOT com DOT au>
Subject: Contributing license information?
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

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?  I have *imagined* that it would be by 
adding a field to every package in setup.ini, something like:

license: "relative-path-to-first-license
relative-path-to-another-license
...
relative-path-to-last-license"

That seems neat to me, since the information is per-package, and AFAIK 
per-package information is stored only in sestup.ini.

If the right way is to modify setup.ini to hold the license info, would 
the new setup.ini require a new setup.exe, or does setup.exe ignore 
information in setup.ini that it doesn't know about?

But I gather that setup.ini is created from other data sources via a 
program called "upset". 

Anyway, what is the right way to contribute this information? 

Regards,

luke

--
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