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