From: Luke Kendall <luke.kendall@cisra.canon.com.au>
To: <cygwin@cygwin.com>
Cc: audit <audit-mail-disclaimer@cisra.canon.com.au>
Subject: Re: Cygwin package naming?
Date: Thu, 01 Sep 2011 08:01:00 -0000 [thread overview]
Message-ID: <4E5F3BB8.8070906@cisra.canon.com.au> (raw)
In-Reply-To: <4E5EE593.1080009@cygwin.com>
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 <http://cygwin.com/setup.html>?
>
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
next prev parent reply other threads:[~2011-09-01 8:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 1:43 Luke Kendall
2011-09-01 1:53 ` Larry Hall (Cygwin)
2011-09-01 2:04 ` Christopher Faylor
2011-09-01 8:01 ` Luke Kendall [this message]
2011-09-01 4:34 ` Charles Wilson
2011-09-01 8:16 ` 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=4E5F3BB8.8070906@cisra.canon.com.au \
--to=luke.kendall@cisra.canon.com.au \
--cc=audit-mail-disclaimer@cisra.canon.com.au \
--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).