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

[Markus H. <mar...@mh...>]

David Nebauer writes:
 > Ah, I see how my choice of words misled you.  I did not want you to make 
 > an upstream change to the install process.  The change I want to make is 
 > only for the Debian install.  The packaging process involves building 
 > the application from source and so I would make the changes only to the 
 > local source tree I am creating the package from.  There are also pre- 
 > and post-install scripts.  The process of adding the links to the /etc 
 > tree is handled by the post-install script.  From what I have observed 
 > of other packages, however, the daemon script is usually copied to the 
 > /etc/init.d directory by the standard install process.  I presume this 
 > involves a simple one-line copy command inserted into one of the make 
 > files.  If you can show me where this command would go I would make the 
 > alteration to my debian build system which would result in the 
 > subsequent deb package copying the daemon to /etc/init.d.
 > 

Ok, I think now I've got it. You need to maintain your own source
branch with the modifications required to install it on Debian. The
required changes should indeed be fairly easy. The most convenient
mechanism is the "install-data-local" hook which allows you to install
a file wherever you like. The following modification of 
scripts/Makefile.am should do what you need to copy refdb to
/etc/init.d (untested, so please beware):

install-data-local:
	$(mkinstalldirs) $(DESTDIR)$(pkgdatadir)/sql
	@for f in $(sqlscripts); do \
		$(INSTALL_DATA) $$f $(DESTDIR)$(pkgdatadir)/sql/$$f; \
	done
	$(INSTALL_DATA) refdb /etc/init.d

Make sure that the leading whitespace of the command is a single
tab. Make is picky about this.

 > This would certainly accomplish the desired result.  Again, however, I 
 > was thinking of something simpler and just for the Debian install: I'd 
 > wget the html manual files from the refdb website and add a copy command 
 > to the build process that would install them as part of the debian 
 > package install.
 > 

Well, if that is kosher, I'll take my time with moving the manual to
XML.

The Makefile modification depends on whether the HTML files are
already available or whether you want the Makefile to retrieve the
files. Assuming the files are available locally (the paths are wild
guesses as I'm away from my Debian test box):

docfiles = $(wildcard *.html)
[...]
install-data-local:
	$(mkinstalldirs) /usr/doc/refdb
	@for f in $(docfiles); do \
		$(INSTALL_DATA) $$f /usr/doc/refdb/$$f; \
	done

 > >- What do libacl1 and libattr1 do?
 > >  
 > >
 > The Debian New Maintainers' Guide gives a couple of commands that 
 > analyse a configure file and extract/construct a list of dependencies:
 > 
 > strace -f -o /tmp/log ./configure
 > for x in `dpkg -S $(grep open /tmp/log|\
 >                       perl -pe 's!.* open\(\"([^\"]*).*!$1!' |\
 >                       grep "^/"| sort | uniq|\
 >                       grep -v "^\(/tmp\|/dev\|/proc\)" ) 2>/dev/null|\
 >                       cut -f1 -d":"| sort | uniq`; \
 >         do \
 >           echo -n "$x (>=" `dpkg -s $x|grep ^Version|cut -f2 -d":"` "), "; \
 >         done
 > 
 > The two packages you queried were included in the output and I accepted 
 > the dependencies "on trust:.  The obvious test is to install refdb on a 
 > debian system lacking these packages and see whether it works.  This is 
 > not practicable as half the system packages depend on these two, either 
 > directly or indirectly.  Since most systems will have these two packages 
 > installed anyway I saw little harm in leaving them in the dependency list.
 > 

Don't take me wrong. I had never heard of these packages, so I was
simply curious what might have caused the dependency. If it is a
Debian peculiarity, it is nothing to worry about for me.

Let me know if you need more specific instructions.

regards,
Markus

-- 
Markus Hoenicka
mar...@ca...
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de