Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com Date: Mon, 22 Feb 1999 14:38:33 -0500 Message-Id: <199902221938.OAA08386@envy.delorie.com> X-Authentication-Warning: envy.delorie.com: dj set sender to dj@envy.delorie.com using -f From: DJ Delorie To: Ssiddiqi@InspirePharm.Com CC: cygwin@sourceware.cygnus.com In-reply-to: <008401be5e87$f1dcd510$29acdfd0@InspirePharm.Com> (Ssiddiqi@InspirePharm.Com) Subject: Re: Cygwin participation threshold References: <008401be5e87$f1dcd510$29acdfd0@InspirePharm.Com> > What about third party products. For example PGI Workstation comes > bundle with Cygwin. Who gets the *paid support* in that case? In cases where companies write software that depends on cygwin, such as the example you give, the potential customer for Cygnus would be that company, for two reasons: (1) they would need a commercial license for cygwin, and (2) they would want a support contract to make sure the cygwin they include in their product doesn't make their product look bad by having bugs. It would be unrealistic to expect each individual user of that software to come to Cygnus for support. More likely, they'd go to the package producer, who may have solutions specific to their software/cygwin bundling, such as a custom-fixed dll. -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com