Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Date: Mon, 22 Aug 2011 21:10:29 +0000 (UTC)
From: "Randall Leeds (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Message-ID: 
 <862772661.2772.1314047429211.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: <4155411.145251294178325740.JavaMail.jira@thor>
Subject: [jira] [Commented] (COUCHDB-1012) Utility to help plugin developers
 manage paths
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Randall Leeds commented on COUCHDB-1012:
----------------------------------------

@Noah:

To re-iterate my position and offer a couple reasons:

The localstate__dir options aren't configurable at build time, they're just created based on localstatedir, so I'll reiterate my desire to exclude them.They're not configurable at runtime, it's generally suggested that they be owned by the couchdb user (therefore not necessarily even readable by someone using this script except at install-with-root-privs time), and deducible from localstatedir.

So my vote is to:
 * Exclude localstate__dir
 * Include package-name or package-identifier so authors can deduce the paths to couch things based on localstatedir, datarootdir, etc...
 * Include elibdir just because by default on *nix we don't install into the default erlang module path but our own private one and we need a name for this place

Then we don't even need any CouchDB-specific anything and it's all in one section.

> 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