Are cygwin packages being pushed to mirrors still compatible with cygwin-2.11.2, now that cygwin-3 has entered the release pipeline?
I have several machines set up with cygwin. (It is a pretty minimal subset: no X, no apache, no big database servers, etc: just basic command line tools.) I try to keep the machines exactly in sync. I generally update cygwin once or twice a year, and sync all the machines to the same version of cygwin at about the same time. I have been doing this for many years, and have a procedure that works well for me. (Roughly, I use cygwin-setup to update one machine, test and burn it in for a few days, and then clone it to the other machines by other means.) I try to avoid the "bleeding edge". I follow the cygwin mailing list, and try _not_ to take a new major version of base cygwin until it settles down, in terms of mailing list traffic. Right now, it feels to me like I should wait awhile before moving to cygwin-3. But now and then I need to upgrade a specific package outside of my full cygwin update cycle. E.g., right now I would like to upgrade just git. So: Assume for the moment that the latest git package release on the mirrors, has been built against cygwin-3 base. Am I reasonably safe to assume it will still work with cygwin-2.11.2? Does this generalize to all, or at least most, other packages? Thank you all for your advice. --- Karl Botts, kdbo...@usa.net -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
