From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10580 invoked by alias); 1 Sep 2011 08:01:14 -0000 Received: (qmail 10572 invoked by uid 22791); 1 Sep 2011 08:01:13 -0000 X-SWARE-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from a.mx.cisra.com.au (HELO EXE01-WPP.cisra.canon.com.au) (203.12.173.71) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 01 Sep 2011 08:00:59 +0000 Received: from EXM01-WVP.cisra.canon.com.au (203.12.172.254) by EXE01-WPP.cisra.canon.com.au (203.12.173.71) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 1 Sep 2011 18:01:09 +1000 Received: from calixa.cisra.canon.com.au (10.11.1.84) by EXM01-WVP.cisra.canon.com.au (10.5.1.208) with Microsoft SMTP Server (TLS) id 14.1.270.1; Thu, 1 Sep 2011 18:00:56 +1000 Message-ID: <4E5F3BB8.8070906@cisra.canon.com.au> Date: Thu, 01 Sep 2011 08:01:00 -0000 From: Luke Kendall User-Agent: Thunderbird 2.0.0.21 (X11/20090302) MIME-Version: 1.0 To: CC: audit Subject: Re: Cygwin package naming? References: <4E5EE340.6010009@cisra.canon.com.au> <4E5EE593.1080009@cygwin.com> In-Reply-To: <4E5EE593.1080009@cygwin.com> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2011-09/txt/msg00009.txt.bz2 Larry Hall (Cygwin) wrote: > On 8/31/2011 9:43 PM, Luke Kendall wrote: >> Can someone with some official Cygwin standing tell me how the Cygwin >> package names correspond with the "official" names of the packages, >> chosen >> by the package owners? In other words, how are the Cygwin package names >> determined? (My hope is that the "official" name is used, possibly with >> "cygwin" added to it in some form.) > > Sorry, I have no badge and gun but perhaps I will do. > >> I'm asking because I'm finding Cygwin packages that contain no license >> information, at least in the compiled form (e.g. gawk, libiconv2). So >> I'm >> thinking that in such cases, I can modify my Cygwin license-finding >> script >> to look up the package by name on freshmeat and try to find the >> license from >> there. >> >> But that is pointless if the Cygwin package name may have the same >> name as a >> freshmeat package, but is in fact some other software. > > How about ? > Thanks! Yes, I think that should be enough (it certainly looks like a public statement of Cygwin's package naming policy, so that's good enough for me): "Package file naming Package naming scheme: use the vendor's version plus a release suffix for ports of existing packages" > Aside: I had to muster all my strength to keep from using the phrase "Use > the source Luke!" I expect you never tire of that. ;-) > > Ah, yes, very true. Not to mention when I eat with my fingers ("Use the forks, Luke!"). Thanks, Larry! 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