Of course! Granted one of the two requires that we maintain a table of
data that is updated continuously and has many significant global
variants and the other is a fairly static definition that can be
traced back to a (relatively) deterministic set of bit patterns.

On Sat, Jun 4, 2011 at 9:42 PM, Jan Lehnardt <j...@apache.org> wrote:
>
> On 5 Jun 2011, at 03:19, Paul Davis wrote:
>
>> Or we write our own code to make HTTP requests (Which isn't out of the
>> question) and remove the curl dependency altogether.
>
> Can we also write our own unicode collation code? :)
>
> Cheers
> Jan
> --
>
>
>>
>> On Sat, Jun 4, 2011 at 9:10 PM, Jan Lehnardt <j...@apache.org> wrote:
>>>
>>> On 4 Jun 2011, at 22:10, Paul Davis wrote:
>>>
>>>> Its already a soft dependency. If curl isn't found all that happens is
>>>> that you can't run ./test/javascript/run after you build it.
>>>
>>> Which means curl is a hard dependency if you want to run the JS tests
>>> that we intend to move from the browser into CLI JS tests, right?
>>>
>>> Cheers
>>> Jan
>>> --
>>>
>>>
>>>>
>>>> On Sat, Jun 4, 2011 at 4:02 PM, Chris Anderson <jch...@apache.org> wrote:
>>>>> This sparks another thought that we could have a ./configure directive
>>>>> that says --no-curl or something. Since we only need curl for purposes
>>>>> of running the developer test suite.
>>>>>
>>>>> Chris
>>>>>
>>>>> On Wed, Jun 1, 2011 at 2:33 PM, Arash Bizhan zadeh <aras...@gmail.com> 
>>>>> wrote:
>>>>>> Hi,
>>>>>> I am trying to compile couch on RH enterprise. The official RH package 
>>>>>> for
>>>>>> curl is 7.15, but Couch needs 7.18. I would like to know what is the best
>>>>>> way to handle this? Is  there any specific reason that Couch depends on
>>>>>> 7.18? Can the dependency be downgraded to 7.15?
>>>>>> Can anybody advise me on how to handle this specific dependency and other
>>>>>> dependencies ( i.e Erlang) please?
>>>>>>
>>>>>> thanks,
>>>>>> -arash
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Chris Anderson
>>>>> http://jchrisa.net
>>>>> http://couchbase.com
>>>>>
>>>
>>>
>
>

Reply via email to