X-Spam-Check-By: sourceware.org
Date: Thu, 2 Feb 2006 22:05:08 -0500
From: Bob Rossi <bob AT brasko DOT net>
To: cygwin AT cygwin DOT com
Subject: Re: mismatched dll
Message-ID: <20060203030508.GF17485@brasko.net>
Mail-Followup-To: cygwin AT cygwin DOT com
References: <020220062158 DOT 387 DOT 43E28079000ACE870000018322007507440A050E040D0C079D0A AT comcast DOT net> <20060203013712 DOT GC17485 AT brasko DOT net> <43E2B779 DOT 4371E33B AT dessent DOT net> <276FEDDB-C5A7-4B38-A82D-025CC97D674E AT rehley DOT net> <43E2C112 DOT CFE77C07 AT dessent DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <43E2C112.CFE77C07@dessent.net>
User-Agent: Mutt/1.5.9i
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

> So, I guess all I'm saying is it's a complicated issue and there is no
> 100% foolproof way to go if you want to be a provider of Cygwin-based
> software that is meant to interact with other Cygwin-based software --
> other than perhaps introducing your software as an official package, or
> telling users to install Cygwin from the cygwin.com mirrors first and
> then integrating with that.  But for some vendors that is too many steps
> and not "turnkey" enough.
> 
> I think at the end of the day, user education as to the nature of the
> problem is really what is required.

Hi Brian,

This is very informative. I do have 1 point to make. Software get's
better and is easier to use, when the user doesn't have to become to
knowledgable about how to install or configure it.

IMHO, Cygwin needs a better way to allow distributers to distribute
software built on top of it. The windows world could see a lot more
smooth open source deliveries if this was possible.

Remember, it only takes 2 open source projects doing the correct thing
to potentially not work in your scenario. Unless both store the
cygwin1.dll in SYSTEM32, or some place where 1 can find the other,
there's going to be problems. Right?

Thanks,
Bob Rossi

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/