On Tuesday 01 March 2005 16:34, Lars Roland wrote:
> 1) How do I create a deb package that just drops the documentation in
> a given directory (eg. it is pure html doc so no man pages are
> created).
easy, just call
dh_install <list_of_files> <destination_without_leading_/>
in your debian/rules file
(if it's a long list of files you might want to put them in
debian/<packagename>.install, after which you just need to call dh_install
without parameters in your debian/rules file)
of course you really should use dh_installdocs instead of plain dh_install
so the doc files get dropped in /usr/share/doc/<packagename> where
debian-users will expect them.
> So I am wondering if anyone has some pointers to
> documentation that explains how to write a deb package from scratch
> without usin the helper tools (as these tools does not seam fit our
> installation procedure).
the helper scripts just move things in the package build directory, you can
always do so by using cp or mv commands explicitly from within your debian
rules file
> 2) When you update the database software from, say, version 1.0 to 1.1
> then it would be preferable to NOT generate all the tables again (that
> is, mysoftware-db 1.1 should just alter or extend the tables that
> mysoftware-db 1.0 created). Can I somehow create a package that
> depends on earlier versions of itself ? - or is there some other
> scheme that is used when you are in a situation where software depends
> on earlier versions of itself ?.
No need to depend on earlier versions, maintainer scripts are called with a
parameter indicating wheter you're newly installing or upgrading (see
section 6.4 of the debian policy document for further info, it will even
tell you the version of the old installed package)
--
Cheers, cobaco (aka Bart Cornelis)
1. Encrypted mail preferred (GPG KeyID: 0x86624ABB)
2. Plain-text mail recommended since I move html and double
format mails to a low priority folder (they're mainly spam)
Attachment:
pgpIdE2GSUTy6.pgp
Description: PGP signature