Mail Archives: cygwin/2008/03/18/19:33:44
On 18/03/2008, Christopher Faylor
<cgf-use-the-mailinglist-please AT cygwin DOT com> wrote:
>
> So, we DON'T WANT people doing this. What we actually want a 3PP to do
> is check if there is a version of cygwin installed and use the installed
> version if it is a newer or conditionally upgrade if it is not.
>
The problem with this is that it requires the immediate and total
cooperation of all 3PPs.
Sure - Acme Software might change their application to check for a
pre-existing instance of Cygwin, and let's say it finds one being used
for KillerApp 1.5. All well and good.
The next time the user re-installs or updates Killer App 1.5, if it
doesn't do the check, it breaks Acme's software.
Unfortunately, KillerApp Co take the view of "well, our software still
works, it must be a problem with Acme".
A package designed to do these checks would certainly be a good idea,
but it isn't going to happen (be adopted) overnight, and in the
meantime, the option of having an isolated cygwin environment is very
alluring. So tempting in fact, that I've been considering recompiling
with a view to stopping 3rd party apps breaking the sshd which is on
our base Win2K3 build.
--
AdamT
I'm the least you could do.
--
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/
- Raw text -