[
https://issues.apache.org/jira/browse/COUCHDB-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13176267#comment-13176267
]
Paul Joseph Davis commented on COUCHDB-1371:
--------------------------------------------
While I understand your general frustration, deleting code just so we don't
have to test a couple versions isn't a convincing argument to me. Though it
does suck having to go back and test older spidermonkeys. I would be up for
"not officially supported, use at your own risk" type of support, though that
just makes me worry that we'll piss off anyone that happens to have an old
SpiderMonkey.
Bottom line, we chose a funky ass dependency years ago and the chickens have
come home to roost. If we want to maintain any semblance of "It just works"
then we'll need to keep maintaining this dependency for quite some time.
> 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
