Re: [Refdb-users] ANN: RefDB RPM packages pulled, packagers wanted

David Nebauer writes:
 > Two things I'd like the Debian install process to do that don't happen 
 > in the current standard install are:
 > 
 > 1.  Install the refdb daemon as well as the relevant links to in the 
 > /etc/init.d|rc?.d tree.  The links are easy to create using the 
 > 'update-rc.d' tool.  What I'd like the make system to handle is the 
 > copying of 'refdb' to '/etc/init.d' and ensuring it has the proper 
 > permissions -- what changes would be required to do this?
 > 

I'm not sure whether installing a daemon should be part of the regular
installation process of a tarball. Daemon installation is all too
OS-dependent. On the BSD's you'd have to use /usr/local/etc/rc.d/ and
rename refdb to refdb.sh, on Windows you have to use a special tool
called cygrunsrv to install refdbd as a service (refdb is not involved
at all), and hell knows how this might work on OSX. If you install
RefDB with the current build process, it is ready to run from the
command line. Everything else should be handled by the OS-specific
port or package code. I'm sure the Debian package system provides a
way to run something like an install script after the
autotools-controlled installation.

 > 2.  Copy a html version of the manual to debian's document system.  What 
 > changes would be required to accomplish this?
 > 

You've found a weak spot that I hoped no one would ever notice. The
documentation is not integrated into the build process so far. I think
about moving the documentation over to DocBook XML and use xsltproc to
transform it. This would not create additional dependencies as we need
xsltproc and the DocBook stylesheets anyway. In that case, "make
install" would put the docs into a directory which would be customizable
with another configure switch.

 > Here are some of the components of the Debian install process as I've so 
 > far designed it.  Please feel free to comment on any changes you think 
 > advisable:
 > 
 > Dependencies:
 > docbook-xsl (>= 1.66.1-1), libacl1 (>= 2.2.23-1), libattr1 (>= 
 > 2.4.16-1), libexpat1 (>= 1.95.8-1), libreadline4-dev (>= 4.3-11), 
 > libxml2 (>= 2.6.16-3), libxml2-utils (>=2.6.16-3), libxml-parser-perl 
 > (>= 2.34-4), zlib1g (>= 1), libdbi0-dev (>= 0.7.2-1), sqlite 
 > (>=2.8.16-1), libdbd-sqlite (>=0.7.1-2), sgml-data (>=2.0.2)
 > 

- What do libacl1 and libattr1 do?
- libxml-parser-perl required for?
- I don't see xsltproc and/or libxslt here?
- isn't libdbi0 required as well to run the drivers?

The remainder looks ok to me. Thanks a lot for tackling this.

regards,
Markus
-- 
Markus Hoenicka
[email protected]
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click