On 20/11/11 20:23, Max Horn wrote: > But I now see that you still maintain boost1.3* packages. Hum, so do you two > coordinate somehow or what?
In so far as the packages should be aware of each other and conflict gracefully. But the boost*cmake and the traditional boost (-bjam) projects are sufficiently different so that one cannot maintain both together. The cmake version seems easier to build, but as usual with cmake, only if you don't have extra wishes like different python versions. The boost-cmake project seemed to be dead with version 1.41, but apparently has risen from the dead now. The boost-cmake web page still has 1.41 as the current version. A Fink boost1.46 package using bjam has also been around for a quite a while (by snaggle, exists in baba's experimental directory). That's the one I haven't got round committing yet. Maybe if boost-cmake really keeps going and produces a decent boost_python lib, I can stop maintaining the bjam version. Maintaining boost is not rewarding. They release a new version every 3 months (current version was 1.48 when I last looked), and they are all incompatible, so each one needs a new package name and they all have to conflict/replace. Many projects that depend on boost require a specific version. There are projects that still require boost-1.35 or even older versions. -- Martin ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net List archive: http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
