[
https://issues.apache.org/jira/browse/COUCHDB-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13088327#comment-13088327
]
Benoit Chesneau commented on COUCHDB-1012:
------------------------------------------
@tilgovi At some point I would prefer to clean myself the patch I've done
though.
To answer to noah . The variables name I've chosen at first was the one you can
find in most of *-config file (incdir, ..). Especially if I some time couchdb
become a full erlang release embedded or not. You don't want to change the
variable meaning each time. Also for a couchdb developers or admin I think it's
more clear to say --db-dir rather than localibdir or whatever is the variable.
Having uri dir is also more useful than having a simple run directory.
couch-config is related to couchdb after-all not a simple generic program.
Anyway let's try to summarize changes here before I go for a patch:
-h --> --help
Other var dirs ? I'm full for this one :
--config-dir configuration directory
--db-dir database directory
--static-dir static asset directory
--doc-dir documentation directory
--erl-libs-dir Erlang library directory
--log-dir log directory
--pid-file daemon PID file
--uri-file daemon sockets file
no real need to add a "couch" namesmace. This is again the *couch-config*
command line. I think it's ok to put here the generated varaiab les during the
configure step. If someone change teh ini file, he already know what to do and
what are paths. Most of devs and admin won't change these variables. I can put
a new patch asap if we are OK with above.
> Utility to help plugin developers manage paths
> ----------------------------------------------
>
> Key: COUCHDB-1012
> URL: https://issues.apache.org/jira/browse/COUCHDB-1012
> Project: CouchDB
> Issue Type: New Feature
> Components: Build System
> Reporter: Randall Leeds
> Assignee: Randall Leeds
> Fix For: 1.2
>
> Attachments:
> 0001-add-couch-config-file-used-to-ease-the-build-of-plug.patch,
> 0001-add-couch-config-file-used-to-ease-the-build-of-plug.patch,
> 0001-support-pkg-config-for-plugins-COUCHDB-1012.patch
>
>
> Developers may want to write plugins (like GeoCouch) for CouchDB. Many hooks
> in the configuration system allow loading arbitrary Erlang modules to handle
> various internal tasks, but currently there is no straightforward and
> portable way for developers of these plugins to discover the location of the
> CouchDB library files.
> Two options that have been proposed are to use pkg-config or install a
> separate script that could be invoked (e.g. as couch-config --erl-libs) to
> discover important CouchDB installation paths.
> As far as I know the loudest argument against pkg-config is lack of support
> for Windows.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
