couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Noah Slater (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COUCHDB-505) Erlang code path prefers older versions of CouchDB
Date Mon, 31 Oct 2011 19:05:33 GMT

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

Noah Slater commented on COUCHDB-505:
-------------------------------------

Also, this is really a bug with Erlang, and should be taken upstream.
                
> Erlang code path prefers older versions of CouchDB
> --------------------------------------------------
>
>                 Key: COUCHDB-505
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-505
>             Project: CouchDB
>          Issue Type: Bug
>    Affects Versions: 0.11
>         Environment: any system where different minor versions of CouchDB have been installed
to the same --prefix
>            Reporter: Adam Kocoloski
>            Assignee: Adam Kocoloski
>             Fix For: 1.2
>
>
> We're using ERL_LIBS to add PREFIX/lib/couchdb/erlang/lib to the code path on CouchDB
startup.  If multiple versions of CouchDB have been installed,  that directory might look
something like
> mochiweb-r97
> ibrowse-1.5.2
> couch-0.9.0
> couch-0.10.0a
> ...
> In this case, we want the system to use beams from couch-0.10.0a, but apparently Erlang's
code loader sorts couch-0.9.0 higher.  
> One solution would be to fall back to explicitly adding specific app directories to the
code path using -pa.
> An elegant solution would be to make sure that our app directories are named in such
a way that they automatically sort correctly in the code loader.  I'm not sure this is really
possible, though, particularly when a user is installing development versions built from source
next to released versions.

--
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

        

Mime
View raw message