[
https://issues.apache.org/jira/browse/COUCHDB-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748844#action_12748844
]
Paul Joseph Davis commented on COUCHDB-216:
-------------------------------------------
Noah,
I think you mean the rel file. The app file is a description of the application
and isn't tied to the Erlang VM. I don't have any experience with Erlang's
release tools, but I'd agree that if it binds to a specific VM then at most we
should just provide a non-standard make target to produce a release.
Keeping the app file up to date *is* a priority as it's used for other things
like detecting conflicting registered processes.
> Make couchdb adhere more to OTP guidelines
> ------------------------------------------
>
> Key: COUCHDB-216
> URL: https://issues.apache.org/jira/browse/COUCHDB-216
> Project: CouchDB
> Issue Type: Improvement
> Reporter: Martin S
> Attachments: 0001-add-couch_app-and-couch_sup.patch,
> 0001-Generate-the-modules-section-of-couch.app-via-the-Ma.patch,
> 0002-add-missing-registered-process-names.patch,
> 0003-make-couchdb-startup-script-use-couch.rel.-load-conf.patch,
> couch_startup_refactor.patch, rearrange.tar.gz
>
>
> CouchDB could adhere to otp standards in a better way.
> Currently we have:
> - couch.app is not uptodate
> - couch_server.erl is an amalgam of 2 behaviours, which is considered being
> "not good".
> From my beginner's perception of OTP, it seems CouchDB is not treated as a
> running application when it is actually running. E.g. appmon doesn't show the
> application once CouchDB is started.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
