[ 
https://issues.apache.org/jira/browse/COUCHDB-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13175833#comment-13175833
 ] 

Randall Leeds commented on COUCHDB-1371:
----------------------------------------

It's true: we have it and it works. However, it is significant testing burden 
in support of something that was released years ago. I'd even pull for dropping 
everything but 1.8.5 on versions of CouchDB that were released after 1.8.5 came 
out, but welcome arguments against it. I'm making significant patches to this 
stuff and it's less than fun to have to test it against three very similar 
versions of SpiderMonkey.

The way I see it there is one good argument for keeping old support: users 
building from source might have the dependency already.
Packagers don't suffer because they often don't update major versions of 
CouchDB between releases anyway and Firefox drives them to get new 
mozilla-central upstream sources periodically anyway. If we make good on all 
the discussion we've had about packaging then we could be solving this for a 
lot of users ourselves anyway. It feels silly for us to triple our testing 
burden to support users that want to compile a shiny new release of CouchDB 
with a three year old SpiderMonkey embedding. End rant.
                
> configure erroneously warns against using a new spidermonkey with old 
> spidermonkeys
> -----------------------------------------------------------------------------------
>
>                 Key: COUCHDB-1371
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1371
>             Project: CouchDB
>          Issue Type: Bug
>            Reporter: Randall Leeds
>            Assignee: Randall Leeds
>            Priority: Minor
>             Fix For: 1.2, 1.3, 1.1.2
>
>         Attachments: 0001-fix-bad-configure-warning-on-old-SpiderMonkey.patch
>
>
> Paul added the check for JSOPTION_ANONFUNFIX in 7ce9e103e, but js-1.7 doesn't 
> have this constant so configure gives a warning.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to