[
https://issues.apache.org/jira/browse/COUCHDB-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12749315#action_12749315
]
Paul Joseph Davis commented on COUCHDB-216:
-------------------------------------------
There are quite a few Erlang tools that require the .app file to be present.
Things like application:start(couchdb) require it. I'm pretty sure appmon
requires it. It may seem unimportant but it breaks a whole bunch of things.
Consider not having a .app file like not having a setup.py in a distributed
Python module.
The .rel stuff I think is orthogonal to making a package for Debian. From what
I've read about Erlang's release tools, it seems like they were designed for
pushing packages to a homogenous environment for hot code upgrades and the
like. As you saw, that kinda breaks down in a Debian style distribution
environment.
Bottom line, the .rel is unimportant, but the .app is quite important.
> 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.
