On 1/4/2014 12:48 PM, S Joshua Swamidass wrote: > The problem with the current cmake approach, though, is that it ignores > the standard python installation mechanism using setuptools. Therefore..
It's a systemic problem. It's not just eggs or pypis, it's jars, debs, cpans, dmgs, and the list goes on and on. You can't reasonably expect people who write the code to also learn suse and redhat and maverick and everyone else's paths and policies and provide packages for all of them. When the whole world is snakes, everything will be packaged in a peepee. Until then the usual procedure is to "make install" into "/tmp/package-root" and then build your .deb, .egg, or .pax in there. Dima ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ OpenBabel-discuss mailing list OpenBabel-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openbabel-discuss
