On Mon, Oct 1, 2012 at 3:38 PM, Dirkjan Ochtman <[email protected]> wrote: > On Mon, Oct 1, 2012 at 3:33 PM, Benoit Chesneau <[email protected]> wrote: >> Not sure what you mean. spidermonkey is choosed on the system while >> snappy is build statically if it's what you mean. My proposal for >> package maintainer is to use the autotools for that. Which would solve >> all of their needs. The autootols here would detect or use the path >> choosen by the package maintainer. While we keep the possibility to >> build static releases. > > Sounds about right. > >> About upstream version, I don't think it's really a problem. We >> shouldn't stop ourself to improve couchdb just because a distributions >> is slow to upgrade to latest stable release. Which doesn't mean we >> should always choose an upstream version. It should be choosed because >> it will improve the user experience. > > I'm not saying you have to wait for distributions to upgrade stuff, I > *am* saying that it would be useful if you get upstream for CouchDB > dependencies to release the fixes you need before releasing the > version of CouchDB that relies on them. And that you then clearly > communicate what versions those are, so that distributors can pick up > the new versions and build everything together. >
Not sure what you mean by " get upstream for CouchDB > dependencies to release the fixes you need before releasing the > version of CouchDB that relies on them. " . supported branches (ie branch -1 like 1.2 today) should have fixes that doesn't update dependencies. 1.3 could have new deps that will be described. - benoit
