You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by Jason Smith <jh...@iriscouch.com> on 2013/02/19 09:15:33 UTC
Understanding the cloudnode build-couchdb branch
Hi, Jan and all,
I am trying to understand the cloudnode branch to build-couchdb. For
reference, see
https://github.com/cloudnode/build-couchdb/commit/fb739d45bee11e87072c0b246719d20cd8cf67d5#commitcomment-2646725
This would be the first commit which alters the CouchDB source code to this
degree, so I am trying to get a deeper understanding of exactly what the
problem is.
Jan, you said you are using this code for your own work. If you or Hans
Schroeder (is he on this lis?) have any feedback I would appreciate it very
much. I am also frustrated with the Mac builds these days.
Thanks.
--
Iris Couch
Re: Understanding the cloudnode build-couchdb branch
Posted by Jason Smith <jh...@iriscouch.com>.
(Basically agree 100% with Benoit, here.)
Hi, Hans. Sorry for not getting the complete picture. Why did this problem
begin in 1.2.1. My master branch (typically) supports the latest OS X. In
your work, did you learn what went "wrong" in 1.2.1?
Thanks!
On Tue, Feb 19, 2013 at 7:46 PM, Hans J Schroeder <hs...@cloudno.de> wrote:
> Hi all,
>
> Agreed, the spawnkillable patch should be applied to the CouchDB repo. It
> is needed for paths that include spaces. This is always the case on OS X
> because the app is called Apache CouchDB.app (with a space) an everything
> is below that path.
>
> - Hans
>
> On Tuesday, February 19, 2013, Benoit Chesneau wrote:
>
> > Patches on couchdb should be made in couchdb if they are really needed
> > and issues open as well if anything should be fixed. Is the quoting
> > around spawnkillable script really needed? Why? I'm curious too.
> >
> > Also embedding rcouch here would do the trick on macosx since....
> > rcouch is fully relocatable and built statically. No need to play with
> > shared libs, env blah blah. There is even a macosx build that I should
> > upgrade ith latest app code. I will publish **on my time** the needed
> > branches for that in couchdb this week. (that and other patches as
> > well). Sorry to not have been able to do that sooner.
> >
> > - benoit
> >
> > On Tue, Feb 19, 2013 at 9:15 AM, Jason Smith <jhs@iriscouch.com
> <javascript:;>>
> > wrote:
> > > Hi, Jan and all,
> > >
> > > I am trying to understand the cloudnode branch to build-couchdb. For
> > > reference, see
> > >
> >
> https://github.com/cloudnode/build-couchdb/commit/fb739d45bee11e87072c0b246719d20cd8cf67d5#commitcomment-2646725
> > >
> > > This would be the first commit which alters the CouchDB source code to
> > this
> > > degree, so I am trying to get a deeper understanding of exactly what
> the
> > > problem is.
> > >
> > > Jan, you said you are using this code for your own work. If you or Hans
> > > Schroeder (is he on this lis?) have any feedback I would appreciate it
> > very
> > > much. I am also frustrated with the Mac builds these days.
> > >
> > > Thanks.
> > >
> > > --
> > > Iris Couch
> >
>
--
Iris Couch
Re: Understanding the cloudnode build-couchdb branch
Posted by Hans J Schroeder <hs...@cloudno.de>.
Hi all,
Agreed, the spawnkillable patch should be applied to the CouchDB repo. It
is needed for paths that include spaces. This is always the case on OS X
because the app is called Apache CouchDB.app (with a space) an everything
is below that path.
- Hans
On Tuesday, February 19, 2013, Benoit Chesneau wrote:
> Patches on couchdb should be made in couchdb if they are really needed
> and issues open as well if anything should be fixed. Is the quoting
> around spawnkillable script really needed? Why? I'm curious too.
>
> Also embedding rcouch here would do the trick on macosx since....
> rcouch is fully relocatable and built statically. No need to play with
> shared libs, env blah blah. There is even a macosx build that I should
> upgrade ith latest app code. I will publish **on my time** the needed
> branches for that in couchdb this week. (that and other patches as
> well). Sorry to not have been able to do that sooner.
>
> - benoit
>
> On Tue, Feb 19, 2013 at 9:15 AM, Jason Smith <jhs@iriscouch.com<javascript:;>>
> wrote:
> > Hi, Jan and all,
> >
> > I am trying to understand the cloudnode branch to build-couchdb. For
> > reference, see
> >
> https://github.com/cloudnode/build-couchdb/commit/fb739d45bee11e87072c0b246719d20cd8cf67d5#commitcomment-2646725
> >
> > This would be the first commit which alters the CouchDB source code to
> this
> > degree, so I am trying to get a deeper understanding of exactly what the
> > problem is.
> >
> > Jan, you said you are using this code for your own work. If you or Hans
> > Schroeder (is he on this lis?) have any feedback I would appreciate it
> very
> > much. I am also frustrated with the Mac builds these days.
> >
> > Thanks.
> >
> > --
> > Iris Couch
>
Re: Understanding the cloudnode build-couchdb branch
Posted by Benoit Chesneau <bc...@gmail.com>.
btw there are other patches needed for ICU:
https://github.com/refuge/couch_core/tree/master/apps/couch/support/patches/icu
On Tue, Feb 19, 2013 at 9:32 AM, Benoit Chesneau <bc...@gmail.com> wrote:
> Patches on couchdb should be made in couchdb if they are really needed
> and issues open as well if anything should be fixed. Is the quoting
> around spawnkillable script really needed? Why? I'm curious too.
>
> Also embedding rcouch here would do the trick on macosx since....
> rcouch is fully relocatable and built statically. No need to play with
> shared libs, env blah blah. There is even a macosx build that I should
> upgrade ith latest app code. I will publish **on my time** the needed
> branches for that in couchdb this week. (that and other patches as
> well). Sorry to not have been able to do that sooner.
>
> - benoit
>
> On Tue, Feb 19, 2013 at 9:15 AM, Jason Smith <jh...@iriscouch.com> wrote:
>> Hi, Jan and all,
>>
>> I am trying to understand the cloudnode branch to build-couchdb. For
>> reference, see
>> https://github.com/cloudnode/build-couchdb/commit/fb739d45bee11e87072c0b246719d20cd8cf67d5#commitcomment-2646725
>>
>> This would be the first commit which alters the CouchDB source code to this
>> degree, so I am trying to get a deeper understanding of exactly what the
>> problem is.
>>
>> Jan, you said you are using this code for your own work. If you or Hans
>> Schroeder (is he on this lis?) have any feedback I would appreciate it very
>> much. I am also frustrated with the Mac builds these days.
>>
>> Thanks.
>>
>> --
>> Iris Couch
Re: Understanding the cloudnode build-couchdb branch
Posted by Benoit Chesneau <bc...@gmail.com>.
Patches on couchdb should be made in couchdb if they are really needed
and issues open as well if anything should be fixed. Is the quoting
around spawnkillable script really needed? Why? I'm curious too.
Also embedding rcouch here would do the trick on macosx since....
rcouch is fully relocatable and built statically. No need to play with
shared libs, env blah blah. There is even a macosx build that I should
upgrade ith latest app code. I will publish **on my time** the needed
branches for that in couchdb this week. (that and other patches as
well). Sorry to not have been able to do that sooner.
- benoit
On Tue, Feb 19, 2013 at 9:15 AM, Jason Smith <jh...@iriscouch.com> wrote:
> Hi, Jan and all,
>
> I am trying to understand the cloudnode branch to build-couchdb. For
> reference, see
> https://github.com/cloudnode/build-couchdb/commit/fb739d45bee11e87072c0b246719d20cd8cf67d5#commitcomment-2646725
>
> This would be the first commit which alters the CouchDB source code to this
> degree, so I am trying to get a deeper understanding of exactly what the
> problem is.
>
> Jan, you said you are using this code for your own work. If you or Hans
> Schroeder (is he on this lis?) have any feedback I would appreciate it very
> much. I am also frustrated with the Mac builds these days.
>
> Thanks.
>
> --
> Iris Couch