This is the mail archive of the
mailing list for the Cygwin project.
Re: cygipc packaging was Updated setup.ini with descriptions, categories, and dependencies
- To: cygwin-apps at cygwin dot com
- Subject: Re: cygipc packaging was Updated setup.ini with descriptions, categories, and dependencies
- From: Christopher Faylor <cgf at redhat dot com>
- Date: Sun, 2 Sep 2001 11:46:32 -0400
- References: <3B8C2682.DE851E18@ece.gatech.edu> <000b01c133a3$0145ec10$7d6707d5@BRAMSCHE>
- Reply-To: cygwin-apps at cygwin dot com
On Sun, Sep 02, 2001 at 01:32:53PM +0200, Ralf Habacker wrote:
>3. Chris wrote:
>>IIRC, the original "authors" got the code from the linux kernel
>>so they couldn't actually assign anything.
>What's than the problem to take this code and integrate it ? Who can made a
Please look at the Contributing link at http://cygwin.com/ . If you
can't fill out an assignment form, the work cannot be integrated with
Cygwin. It's that simple.
It's not my decision but I have to enforce it.
I have my famous "mixed feelings" about including the cygipc package as
a downloadable option for cygwin. If people are accustomed to thinking
that it is part of cygwin, I think that the incentive for writing our
own daemon is going to be much less. And, we really do need our own
daemon for doing a lot of things.
So, my feeling is that cygipc should not be included by default.
However, I am willing to be swayed in this decision if the other
developers think that it really would be a good idea to include it. To
be clear -- we can't release it as part of cygwin itself but we could
release it as a separate package.