This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Cygwin package naming?
- From: "Larry Hall (Cygwin)" <reply-to-list-only-lh at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 31 Aug 2011 21:53:23 -0400
- Subject: Re: Cygwin package naming?
- References: <4E5EE340.6010009@cisra.canon.com.au>
- Reply-to: cygwin at cygwin dot com
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 <http://cygwin.com/setup.html>?
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. ;-)
--
Larry
_____________________________________________________________________
A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
--
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