incubator-couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Randall Leeds (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COUCHDB-1012) Utility to help plugin developers manage paths
Date Sat, 20 Aug 2011 10:54:27 GMT

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

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

I think we're getting carried away.

localstatelibdir (db-dir), localstatelogdir (log-dir) should disappear from here. localstatedir
is the only variable that matters to autotools[1] and we don't even accept the others as flags
to configure. I'd drop pid-file, uri-file and all the autotools stuff because it's not relevant
for developing _modules_ for couchdb. It's relevant for building and running couchdb, when
the values are either being passed by the packager or set by the operator.

Something like --libdir to mean the erlang lib dir for all the erlang modules we install and
--configdir to be the directory containing local.d and default.d.

That's all developers should need. If developers of plugins want to install documentation
of various formats they can do their own autotools dance. The documentation and supporting
tooling or whatever else somone might package together with a couchdb module and how they
distribute it is not our concern, but unless we provide a way for developers to modify the
erlang code path we need them to install to our --libdir. Otherwise, it's just erlang modules
that couch can load via its hooks in the .ini system. We shouldn't overthink this.

[1] https://www.gnu.org/s/hello/manual/autoconf/Installation-Directory-Variables.html

> 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: Noah Slater
>             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

        

Mime
View raw message