[
https://issues.apache.org/jira/browse/COUCHDB-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086465#comment-13086465
]
Noah Slater commented on COUCHDB-1012:
--------------------------------------
Providing aliases for these environment variables is just going to muddy the
water and potentially confuse people more. If you look at the output. The
values here should precisely match the output from ./configure --help, which I
did not think of checking before. Let me check that right now, as I write this
very sentence.
This is the output:
Fine tuning of the installation directories:
--bindir=DIR user executables [EPREFIX/bin]
--sbindir=DIR system admin executables [EPREFIX/sbin]
--libexecdir=DIR program executables [EPREFIX/libexec]
--sysconfdir=DIR read-only single-machine data [PREFIX/etc]
--sharedstatedir=DIR modifiable architecture-independent data [PREFIX/com]
--localstatedir=DIR modifiable single-machine data [PREFIX/var]
--libdir=DIR object code libraries [EPREFIX/lib]
--includedir=DIR C header files [PREFIX/include]
--oldincludedir=DIR C header files for non-gcc [/usr/include]
--datarootdir=DIR read-only arch.-independent data root [PREFIX/share]
--datadir=DIR read-only architecture-independent data [DATAROOTDIR]
--infodir=DIR info documentation [DATAROOTDIR/info]
--localedir=DIR locale-dependent data [DATAROOTDIR/locale]
--mandir=DIR man documentation [DATAROOTDIR/man]
--docdir=DIR documentation root [DATAROOTDIR/doc/apache-couchdb]
--htmldir=DIR html documentation [DOCDIR]
--dvidir=DIR dvi documentation [DOCDIR]
--pdfdir=DIR pdf documentation [DOCDIR]
--psdir=DIR ps documentation [DOCDIR]
I contend that the output of this script should be:
--bindir user executables [EPREFIX/bin]
--sbindir system admin executables [EPREFIX/sbin]
--libexecdir program executables [EPREFIX/libexec]
--sysconfdir read-only single-machine data [PREFIX/etc]
--sharedstatedir modifiable architecture-independent data [PREFIX/com]
--localstatedir modifiable single-machine data [PREFIX/var]
--libdir object code libraries [EPREFIX/lib]
--includedir C header files [PREFIX/include]
--oldincludedir C header files for non-gcc [/usr/include]
--datarootdir read-only arch.-independent data root [PREFIX/share]
--datadir read-only architecture-independent data [DATAROOTDIR]
--infodir info documentation [DATAROOTDIR/info]
--localedir locale-dependent data [DATAROOTDIR/locale]
--mandir man documentation [DATAROOTDIR/man]
--docdir documentation root [DATAROOTDIR/doc/apache-couchdb]
--htmldir html documentation [DOCDIR]
--dvidir dvi documentation [DOCDIR]
--pdfdir pdf documentation [DOCDIR]
--psdir ps documentation [DOCDIR]
I would also update the help description to read:
The $basename command runs the %package_name% environment tool.
When %package_name% is installed, certain environment variables are set.
This script will display the current values of those variables.
See the %package_name% ./configure --help output for more information.
The exit status is 0 for success or 1 for failure.
> 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
