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 22:26:27 GMT

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

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

I'm just going to trust Noah here, but I'd like to see CouchDB-specific options listed first
and to see the reconfigurable options left out: localstate*dir.
I think localdatadir needs to be there, but should be renamed to reflect what it is: static
resources used by the HTTP server (futon, js tests, etc). Not sure what name that should be.

How about this list:

CouchDB variables:
  --couchconfdir configuration data [SYSCONFDIR/$package_identifier]
  --couchstaticroot runtime data [DATADIR/$package_identifier]
    ^^ please help me name this one
  --couchlibdir library data [LIBDIR/$package_identifier]
    ^^ this should be the ..../erlang/lib dir, either the system erlang (Windows and CentOS
packages do this) or Couch's private one in LIBDIR/couchdb/erlang/lib

Other variables:

  We don't install to most of these. It's strange to me that autoconf still generates a configure
with all these options even when we don't use most of them.
  I'm fine with keeping any and all of them, as long as we list it after the CouchDB ones.
  --libexecdir program executables [EPREFIX/libexec]
  --sharedstatedir modifiable architecture-independent data [PREFIX/com]
  --infodir info documentation [DATAROOTDIR/info]
  --localedir locale-dependent data [DATAROOTDIR/locale]
  --docdir documentation root [DATAROOTDIR/doc/apache-couchdb]
  --htmldir html documentation [DOCDIR]
  --dvidir dvi documentation [DOCDIR]
  --pdfdir pdf documentation [DOCDIR]
  --psdir ps documentation [DOCDIR]

Is this getting closer?

> 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