On Sun, 20 Sep 2009, Szak�ts Viktor wrote:
[...]
Usually in system installation we have existing structure like:
<instpref>/bin - with executable files, one of PATH dirs
we should not use any subdirectories here
<instpref>/lib - with shared libraries, one of system library dirs
we can use subdirectory for static libraries and
it's even suggested to reduce name conflicts
but native shared library have to be in this
localization
<instpref>/include - with header files, we can and should use subdir
for our own header files
<instpref>/share/man - with man files - sub dirs with strict meaning and
naming convention. Sometimes it's without share
<instpref>/man (i.e. in /usr/local)
<instpref>/share/doc - with non man documentation, we should use subdir
<instpref>/etc - with configuration files, if necessary it's
possible to use subdirs with the exception to
/usr which stores configuration files in /etc
FHS suggests also to use /etc/opt and /etc/local
for configurations files from /opt /usr/local
For applications which can be globally accessed it's suggested to move
configuration files into '/etc' directory. It helps in creating backups
but also in locating configuration files by other programs bound with
given application, i.e. in our case we may talk about final user
applications compiled by Harbour which may look for some system global
Harbour configuration files, i.e. now /etc/harbour/hb-charmap.def which
is used optionally by some GTs like GTCRS or GTTRM (for details look at
source/rtl/gtcrs/hb-charmap.def, I plan to introduce also hb-keymap.def
and hb-termmap.def for GTTRM what should allow to configure some unknown
for GTTRM terminals by users or system admins) and I would like to keep
/etc/harbour as default global harbour configuration directory though
for packages installed in '/opt' FHS suggests to use '/etc/opt'.
It's not easy to create rules which can follow exactly different
distribution policy so we should give an interface to set each of the
above directory separately. It means that we have to introduce yet
two new envvars for man and configurations files, i.e. HB_MAN_INSTALL
and HB_ETC_INSTALL or HB_CNF_INSTALL.
Building RPM packages we have predefined macros like %{_bindir}, %{_libdir},
%{_includedir}, %{_mandir}, %{_sysconfdir}, %{_defaultdocdir}, ... which
can be used to set our own HB_*_INSTALL variables to suggested system
directories without touching HB_INSTALL_PREFIX so it's not a problem.
We do not use autoconf so we have to chose sth ourselves for 'manual'
installation using only HB_INSTALL_PREFIX. We have to remember also
that at runtime hbmk2 may need to replicate some parts of our detection
logic.
Here are 4 system wide installations which can be used in different
*nixes and try to confirm FHS as close as possible.
'->' means soft link,
1. FHS2.3 compliant localization for add-on applications:
=========================================================
/opt/
/harbour/
/bin/
<harbour_executable_files>
/lib/
<native_harbour_libraries>
[/<addon_harbour_lib>/
<native_addon_libraries>]
[/<platform>/<cc>/
<platform_cc_libraries>]
/include/
<harbour_header_files>
[/<addon_harbour_lib>/
<addon_header_files>]
/share/
/man/
/man1/
<harbour_man_pages>.1
/doc/
<harbour_doc_files_and_dirs>
[/<addon_harbour_lib>/
<addon_docs>]
/etc -> /etc/harbour
/etc/
/harbour/
<harbour_config_files>
/etc/
/opt/ (if exists)
/harbour -> /etc/harbour
if /opt/bin exists then we should create in this directory soft links
to executable files in /opt/harbour/bin
if /opt/lib exists then we should create in this directory soft links
to harbour shared libraries in /opt/harbour/lib
if /opt/man/man1 exists then we should create in this directory soft links
to harbour shared libraries in /opt/harbour/share/man/man1
2. FHS2.3 compliant localization for distribution applications:
===============================================================
/usr/
/bin/
<harbour_executable_files>
/lib/
<soft_links_to_native_harbour_shared_libraries>
/harbour/
<native_harbour_libraries>
[/<addon_harbour_lib>/
[/<platform>/<cc>/
<platform_cc_libraries>]
/include/
/harbour/
<harbour_header_files>
[/<addon_harbour_lib>/
<addon_header_files>]
/share/
/man/
/man1/
<harbour_man_pages>.1
/doc/
/harbour/
<harbour_doc_files_and_dirs>
[/<addon_harbour_lib>/
<addon_docs>]
/etc/
/harbour/
<harbour_config_files>
In some systems instead of /usr/share/doc/harbour we should use
/usr/share/doc/packages/harbour.
Such localization (tuned by system settings in package manager)
is used now by RPM and DEB packages
3. FHS2.3 compliant localization for local applications
(BSD compatible localization for non core packages):
=======================================================
/usr/
/local/
/bin/
<harbour_executable_files>
/lib/
<soft_links_to_native_harbour_shared_libraries>
/harbour/
<native_harbour_libraries>
[/<addon_harbour_lib>/
[/<platform>/<cc>/
<platform_cc_libraries>]
/include/
/harbour/
<harbour_header_files>
[/<addon_harbour_lib>/
<addon_header_files>]
/man/
/man1/
<harbour_man_pages>.1
/share/
/doc/
/harbour/
<harbour_doc_files_and_dirs>
[/<addon_harbour_lib>/
<addon_docs>]
/etc/
/harbour -> /etc/harbour
/etc/
/harbour/
<harbour_config_files>
/etc/
/local/ (if exists)
/harbour -> /etc/harbour
4. HAIKU localization for non system core packages
==================================================
/boot/
/common/
/bin/
<harbour_executable_files>
/lib/
<soft_links_to_native_harbour_shared_libraries>
/harbour/
<native_harbour_libraries>
[/<addon_harbour_lib>/
[/<platform>/<cc>/
<platform_cc_libraries>]
/include/
/harbour/
<harbour_header_files>
[/<addon_harbour_lib>/
<addon_header_files>]
/share/
/man/
/man1/
<harbour_man_pages>.1
/doc/
/harbour/
<harbour_doc_files_and_dirs>
[/<addon_harbour_lib>/
<addon_docs>]
/etc/
/harbour/
<harbour_config_files>
'share/man' can be replaced by 'man'.
Solaris does not support /usr/local, suggested localization: 1
*BSD does not support /opt, suggested localization: 3
Darwin suggested localization: 1 (please confirm)
Linux suggested localization: DEB/RPM->2 (tuned by package manager),
1 or 3 for non package installation.
HPUX 1 or 3 I do not know which is preferred and which lib dirs
in SHLIB_PATH/LD_LIBRARY_PATH
HAIKU does not support /usr and /opt, suggested localization: 4
AIX suggested localization: modified 1 (/opt/freeware instead of /opt)
but details should be verified by real AIX users
For non system installation we can chose any directory structure though
probably the easiest method is using the same tree as in /opt/harbour
(version 1).
The shard library naming convention
===================================
@ - softlink
* - hardlink
@<pref><name><epoc>.<ext> ->
@<pref><name><epoc>.<ext>.<major> ->
@<pref><name><epoc>.<ext>.<major>.<minor> ->
*<pref><name><epoc>.<ext>.<major>.<minor>.<rev>
<pref> is library name prefix,
'lib' in supported by Harbour *nix systems
<name> is base name, 'harbour' in our case
<epoc> is used to mark new or alternative branches, we are using
'mt' to mark alternative libraries with MT support.
<ext> is library extension,
'dylib' in Darwin,
'sl' in HP-UX,
'so' in others.
<major>, <minor>, <rev> - version numbers (i.e. 2.0.0 for current SVN).
i.e.:
@libharbour.so ->
@libharbour.so.2 ->
@libharbour.so.2.0 ->
*libharbour.so.2.0.0
Real/suggested usage in supported *nixes:
Linux, Solaris, Haiku, NetBSD:
@<pref><name><epoc>.<ext> -> *
@<pref><name><epoc>.<ext>.<major> ->
*<pref><name><epoc>.<ext>.<major>.<minor>.<rev>
FreeBSD (some packages use Linux like form):
@<pref><name><epoc>.<ext> ->
*<pref><name><epoc>.<ext>.<major>
OpenBsd:
*<pref><name><epoc>.<ext>.<major>.<minor>
Darwin???
HP-UX???
best regards,
Przemek
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
