[
https://issues.apache.org/jira/browse/COUCHDB-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086469#comment-13086469
]
Noah Slater commented on COUCHDB-1012:
--------------------------------------
Oh, forgot to mention, I don't think it matters that we don't necessarily use
all of these variables for anything. It maintains consistency with out build
system that sets them in the first place. Also, from these, and knowing where
CouchDB puts files, you can work out where CouchDB specific sub-directories
are. If you can't work out how to get from localstatedir to the place CouchDB
keeps it's .couch files, you're not the intended audience for this script.
> 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
