couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Benoit Chesneau <>
Subject dependancy tracking
Date Wed, 20 Jun 2012 15:16:36 GMT
In my last attempt to make the core more erlangish, I'm trying to find
a way to manage dependencies like webmachine, oauth, snappy, ... . I
thought one way would be to get them while preparing the release like
I do in rcouch, but maybe some still want to have them in the


1. What do you prefer ?
   a. keep the dependency in the source
   b. getting them at the release (with possibly rebar), they will be
distributed with the archive

2. In case of a), is there a good pattern to maintain/track changes
upstreams ? We for now do big merge, without keeping upstream history.
It may be a problem or not. Thought?

- benoit

View raw message