X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Message-ID: <4EA0D2AB.30402@cisra.canon.com.au> Date: Fri, 21 Oct 2011 13:02:19 +1100 From: Luke Kendall User-Agent: Thunderbird 2.0.0.21 (X11/20090302) MIME-Version: 1.0 To: CC: audit Subject: Re: Contributing license information? References: <4E4DB7AC DOT 7070702 AT cisra DOT canon DOT com DOT au> <20110819120318 DOT GB2506 AT calimero DOT vinschen DOT de> <4E9F9A2A DOT 2060806 AT cisra DOT canon DOT com DOT au> <20111020073807 DOT GC23092 AT calimero DOT vinschen DOT de> In-Reply-To: <20111020073807.GC23092@calimero.vinschen.de> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Corinna Vinschen wrote: > 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. > > Okay. So in reply to your later email, I will plan to provide the added information about licenses into the base-files package, instead of creating a new one. (I hope I have understood you correctly!) Can I ask a related question: for the few shell scripts and /etc files provided in base-files: what license are they under? The package contains lots of licenses, as we've been discussing, but I couldn't find any indication of which license applies to the actual non-license files in base-files itself! Regards, luke > Corinna > > -- 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