On Wed, January 24, 2007 3:55 pm, Tracy R Reed wrote: > Andrew Lentvorski wrote: >> If you are developing software, you have to *know* your dependency >> chain. Choosing a dependency of "RedHat Enterprise Linux 4" gets you in >> massive trouble when something breaks. > > The version control a piece of software was built with is usually not > considered a dependency of the software, right? People who install > Windows have no idea what MS uses for version control, for example. >
Absolutely. The issue, if I may presume to speak for others, is that the svn dev team, alas, cannot seem to stabilize what they develop against and are always upgrading their dev environment to the latest, shiniest, newest libs and tools. This means if one has, say, a plain old FC5 box (how incredibly ... DECEMBER '06!), the upgrade can go into dependency hell on you. I prefer teams who pick a stock release as their platform and don't get cutesy. I can't believe that every new trinket is actually necessary for their development. Oh, well, the product is worth some aggrivation. But the aggrivation is IMHO probably not necessary. -- Lan Barnes SCM Analyst Linux Guy Tcl/Tk Enthusiast Biodiesel Brewer -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
