Re: cygipc packaging was Updated setup.ini with descriptions, categories, and dependencies

[Charles Wilson <cwilson at ece dot gatech dot edu>]

Christopher Faylor wrote:


> 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.


I agree with Chris (mostly), except that I lean more to the middle.  I 
*would* believe that cygipc should not be included (as an 
official-but-separate package, yadda yadda yadda) -- except that IF the 
conditions I outlined in my earlier message are met, then I get to 
relinquish maintaining a package!  (So, there's a bit of self-interest 
there).

Currently, even though cygipc is not an official package, I do maintain 
it, incorporate new patches, field email onlist and off, etc.  IF 
someone else were to volunteer to take over that maintainership, then 
I'd help that person package cygipc up as an official 
(setup-installable, cygwin-mirrors style) package.  And then step back 
and let "the new maintainer" handle it from there.

So, while I think that adding cygipc as an "official" package will 
detract from other forward progress (the cygwin daemon, etc) and is a 
marginally bad thing, my self-interest in giving up maintainership of a 
package pushes me to be more positively inclined than I might otherwise be.

--Chuck