This is the mail archive of the
cygwin-apps@cygwin.com
mailing list for the Cygwin project.
Re: How to create a ksh93 package...
- From: Christopher Faylor <cgf at redhat dot com>
- To: cygwin-apps at cygwin dot com
- Date: Wed, 27 Mar 2002 21:21:25 -0500
- Subject: Re: How to create a ksh93 package...
- References: <00c301c1d5e8$038b6300$f20114d5@muffin> <20020328000656.GC2331@redhat.com> <3CA25F67.80608@ece.gatech.edu>
- Reply-to: cygwin-apps at cygwin dot com
On Wed, Mar 27, 2002 at 07:10:15PM -0500, Charles Wilson wrote:
>> Do we really need to install other UNIX-like utilities? That will be
>> very confusing for users, I think. Can't ksh just use the existing
>utilties?
>
>Remember ksh has that in-process execution thing, where certain commands
>are replaced by internally loadable modules...the stuff Robert was
>talking about two weeks ago.
True, but there is no reason to call "ls.exe" by the same name in
another directory. It could be called "ksh-ls.exe" or or ls.so or
something.
>>>Would it be OK to create a dummy -src package that just contains a text
>>>file (maye be with a suspicious name) which refers to the AT&T software
>>>download site?
>
>Absolutely not. We must distribute the sources OURSELVES in order to
>comply with our own cygwin GPL license!
Cygwin doesn't really GPL infect anything. If the source license that ksh93
is distributed with allows downloading from a web site, then that's fine,
so there is no reason to be GPL compliant.
What matters is if the source license is compliant under the exception
that Cygwin provides.
cgf