On Tue, Jun 21, 2011 at 7:34 PM, Noah Slater wrote:
>
> On 21 Jun 2011, at 17:55, Benoit Chesneau wrote:
>
>> It would on the contrary conciliate
>> both targets and I think can provide an easy way to build a release
>> while being more erlangish.
>
> As I have said before, if we can make the Erla
[
https://issues.apache.org/jira/browse/COUCHDB-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052798#comment-13052798
]
Markus Barchfeld commented on COUCHDB-1017:
---
Thanks for your comment, Gabriel.
On 21 Jun 2011, at 17:55, Benoit Chesneau wrote:
> It would on the contrary conciliate
> both targets and I think can provide an easy way to build a release
> while being more erlangish.
As I have said before, if we can make the Erlang part of the CouchDB build more
Erlangish, I am all for that
On Tue, Jun 21, 2011 at 6:38 PM, Noah Slater wrote:
>
> On 21 Jun 2011, at 17:17, Benoit Chesneau wrote:
>
>> I don't buy this argument. CouchDB is an erlang application. It's true
>> that it target different kind of population and not only the
>> developer. If we consider that couchdb is an erlan
On 21 Jun 2011, at 17:17, Benoit Chesneau wrote:
> I don't buy this argument. CouchDB is an erlang application. It's true
> that it target different kind of population and not only the
> developer. If we consider that couchdb is an erlang application (and
> it is really) we could just use the too
On Jun 21, 2011, at 11:24 AM, Paul Davis wrote:
> On Tue, Jun 21, 2011 at 10:54 AM, Robert Dionne
> wrote:
>> Thanks Paul, was just going to respond about /rel
>>
>> My two cents:
>>
>> I think what would be nice is to enable the use of rebar in downstream
>> projects, that are built on top
On Tue, Jun 21, 2011 at 5:59 PM, Noah Slater wrote:
>
> On 21 Jun 2011, at 16:19, Benoit Chesneau wrote:
>
>> why not at top level? Currently everything is an src folder and I
>> don't see any reason except arbitrary concern? Why split everything in
>> folders that have not really a sense here ?
>
On 21 June 2011 17:05, Noah Slater wrote:
>
> On 21 Jun 2011, at 16:46, Dale Harvey wrote:
>
> > + src
> > + ebin
> > + couch.app
> > + lib
> > + ejson
> > + src
> > + ibrowse
> > + src
>
> Too much root directory pollution, still. I think we should have two main
> top level directori
On Tue, Jun 21, 2011 at 11:59 AM, Noah Slater wrote:
>
> On 21 Jun 2011, at 16:19, Benoit Chesneau wrote:
>
>> why not at top level? Currently everything is an src folder and I
>> don't see any reason except arbitrary concern? Why split everything in
>> folders that have not really a sense here ?
On 21 Jun 2011, at 16:46, Dale Harvey wrote:
> + src
> + ebin
> + couch.app
> + lib
> + ejson
> + src
> + ibrowse
> + src
Too much root directory pollution, still. I think we should have two main top
level directories for the Erlang files. We should use src/ for the main CouchDB
so
On 21 Jun 2011, at 16:19, Benoit Chesneau wrote:
> why not at top level? Currently everything is an src folder and I
> don't see any reason except arbitrary concern? Why split everything in
> folders that have not really a sense here ?
Because there is a misconception here.
CouchDB is not an Er
In the interest of keeping small changes, I would have thought it would be
very easy to do a renaming of the source level directory layout to as
proposed (I have no strong opinion on rel/ priv/ etc)
+ src
+ ebin
+ couch.app
+ lib
+ ejson
+ src
+ ibrowse
+ src
and keep the build t
On Tue, Jun 21, 2011 at 4:25 PM, Paul Davis wrote:
> On Tue, Jun 21, 2011 at 2:25 AM, Benoit Chesneau wrote:
>> Hi all,
>>
>> I'm back on this topic. I know that @davisp made a script to split the
>> file structure etc, but I wonder why or what we are waiting to do
>> this. Also why using a scrip
On Tue, Jun 21, 2011 at 10:54 AM, Robert Dionne
wrote:
> Thanks Paul, was just going to respond about /rel
>
> My two cents:
>
> I think what would be nice is to enable the use of rebar in downstream
> projects, that are built on top of couchdb. I've been able to keep my
> bitstore[1] hack prett
On Tue, Jun 21, 2011 at 4:54 PM, Robert Dionne
wrote:
> Thanks Paul, was just going to respond about /rel
>
> My two cents:
>
> I think what would be nice is to enable the use of rebar in downstream
> projects, that are built on top of couchdb. I've been able to keep my
> bitstore[1] hack pretty
On Tue, Jun 21, 2011 at 10:37 AM, Noah Slater wrote:
>
> On 21 Jun 2011, at 15:31, Paul Davis wrote:
>
>> Perhaps we should just write a small tool that does the
>> compilation in parallel instead of trying to wedge a square hole into
>> a hypercube.
>
> GNU Make has parallel builds baked in.
>
>
On Tue, Jun 21, 2011 at 4:25 PM, Paul Davis wrote:
> On Tue, Jun 21, 2011 at 2:25 AM, Benoit Chesneau wrote:
>> Hi all,
>>
>> I'm back on this topic. I know that @davisp made a script to split the
>> file structure etc, but I wonder why or what we are waiting to do
>> this. Also why using a scrip
Thanks Paul, was just going to respond about /rel
My two cents:
I think what would be nice is to enable the use of rebar in downstream
projects, that are built on top of couchdb. I've been able to keep my
bitstore[1] hack pretty much in sync with a given
couchdb version with some simple tweaks
On Tue, Jun 21, 2011 at 10:30 AM, Noah Slater wrote:
>
> On 21 Jun 2011, at 15:25, Paul Davis wrote:
>
>> The problem with 'doing it once' is that its not entirely that
>> straight forward unless you want to have a single absolutely massive
>> commit. And that's something I wanted to avoid.
>
> Ca
On 21 Jun 2011, at 15:31, Paul Davis wrote:
> Perhaps we should just write a small tool that does the
> compilation in parallel instead of trying to wedge a square hole into
> a hypercube.
GNU Make has parallel builds baked in.
http://developers.sun.com/solaris/articles/parallel_make.html
On Tue, Jun 21, 2011 at 5:51 AM, Benoit Chesneau wrote:
> On Tue, Jun 21, 2011 at 10:05 AM, Randall Leeds
> wrote:
>> I like this.
>> I'd love to see a branch that contains all the incremental changes
>> from trunk to this build.
>> I would build and test it and help you work out any kinks.
>>
>
On 21 Jun 2011, at 15:25, Paul Davis wrote:
> The problem with 'doing it once' is that its not entirely that
> straight forward unless you want to have a single absolutely massive
> commit. And that's something I wanted to avoid.
Can we break this work down into logical chunks?
We could transit
On Tue, Jun 21, 2011 at 2:25 AM, Benoit Chesneau wrote:
> Hi all,
>
> I'm back on this topic. I know that @davisp made a script to split the
> file structure etc, but I wonder why or what we are waiting to do
> this. Also why using a script when we could move everything once? (and
> it should be d
On 21 Jun 2011, at 10:51, Benoit Chesneau wrote:
> - @davisp will it be possible with the passage from svn to git to
> maintain multiple repos on couchdb project ? eg: repos for ejson and
> snappy-erlang ? For now I include them in the deps folder anyway, but
> it may be better to sepratae them a
On 21 Jun 2011, at 07:39, Fedor Indutny wrote:
> +1 for that, I don't like current directory structure.
Which bit, and why?
On 21 Jun 2011, at 07:25, Benoit Chesneau wrote:
> c_src/{couchjs, icu, spawnkillable?}
I don't understand why you need this directory.
Why can't these things be kept in the main src/ directory?
> etc/
> tests/
> bin/couch
I am confused as to why you have included directories like these.
It
[
https://issues.apache.org/jira/browse/COUCHDB-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052560#comment-13052560
]
Gabriel Farrell commented on COUCHDB-1017:
--
Benoit, works for me. Which commit
The only thing I can say is: +1 big time on this one :)
On Tue, Jun 21, 2011 at 5:56 AM, Benoit Chesneau wrote:
> On Tue, Jun 21, 2011 at 11:51 AM, Benoit Chesneau wrote:
>> On Tue, Jun 21, 2011 at 10:05 AM, Randall Leeds
>> wrote:
>>> I like this.
>>> I'd love to see a branch that contains al
[
https://issues.apache.org/jira/browse/COUCHDB-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Filipe Manana resolved COUCHDB-1199.
Resolution: Fixed
Fix Version/s: 1.2
1.1.1
Fix applied to trunk
On Tue, Jun 21, 2011 at 11:51 AM, Benoit Chesneau wrote:
> On Tue, Jun 21, 2011 at 10:05 AM, Randall Leeds
> wrote:
>> I like this.
>> I'd love to see a branch that contains all the incremental changes
>> from trunk to this build.
>> I would build and test it and help you work out any kinks.
>>
On Tue, Jun 21, 2011 at 10:05 AM, Randall Leeds wrote:
> I like this.
> I'd love to see a branch that contains all the incremental changes
> from trunk to this build.
> I would build and test it and help you work out any kinks.
>
Hi,
Cool. I've create a branch on my github here :
https://github.
[
https://issues.apache.org/jira/browse/COUCHDB-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052442#comment-13052442
]
Marcello Nuccio commented on COUCHDB-1175:
--
Jason, I am still convinced that fu
[
https://issues.apache.org/jira/browse/COUCHDB-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052438#comment-13052438
]
Filipe Manana commented on COUCHDB-1175:
Hi Jason,
The resulting list not only
I like this.
I'd love to see a branch that contains all the incremental changes
from trunk to this build.
I would build and test it and help you work out any kinks.
On Mon, Jun 20, 2011 at 23:39, Fedor Indutny wrote:
> +1 for that, I don't like current directory structure.
>
> Cheers,
> Fedor.
>
34 matches
Mail list logo
