couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Adam Kocoloski <kocol...@apache.org>
Subject Re: tracking upstream dependencies
Date Sat, 27 Nov 2010 17:00:08 GMT
Not exactly what you asked for, but I think it can accomplish the same purpose:

https://github.com/cloudant/bigcouch/compare/apache:1.0.1...cloudant:master

Best, Adam

On Nov 27, 2010, at 5:27 AM, Robert Newson wrote:

> I like the Debian approach where they maintain a patchset against a
> pristine upstream tarball.
> 
> I'd particularly like to see the bigcouch variant of couchdb expressed
> that way, it would allow new developers to see where bigcouch diverges
> and it would allow couchdb developers to easily incorporate generally
> useful patches.
> 
> B.
> 
> On Fri, Nov 26, 2010 at 9:25 PM, Dirkjan Ochtman <dirkjan@ochtman.nl> wrote:
>> On Fri, Nov 26, 2010 at 22:15, Noah Slater <nslater@apache.org> wrote:
>>> If we have a checksum, what's the point?
>>> 
>>> Why not just include the original source the checksum is taken from?
>> 
>> The point is keeping very exact track of what the source is. And the
>> point is making it easy for distributors to build without the bundled
>> dependencies. It would be great to also ship an artefact without the
>> bundled deps, but that might be a tad too much work...
>> 
>> Cheers,
>> 
>> Dirkjan
>> 


Mime
View raw message