[ Just a couple of comments, on an otherwise v. helpful answer ]
Fabrizio Polacco <[EMAIL PROTECTED]> writes:
> > So what special work do library packages need, before I get in too far
> > over my head?
[ ... ]
> link the shared lib using
> -shared -Wl,-soname,libgc4.so.4 -o libgc4.so.4.13alpha1
add "-lc", and run dpkg-shlibdeps on the library with
${shlibs:Depends} in the Depends: line in debian/control.
> but without -rpath (which is considered harmful).
Indeed.
> Install in debian/tmp/DEBIAN a postinst with the instruction
> ldconfig
*Iff* "$1" = "configure"; try something like:
| 23:48:[EMAIL PROTECTED]| ~ $cat /var/lib/dpkg/info/libpam0g.postinst
| #! /bin/sh
|
| set -e
|
| case "$1" in
| configure)
| ldconfig
| ;;
| abort-upgrade|abort-remove|abort-deconfigure)
| ;;
| esac
| 23:48:[EMAIL PROTECTED]| ~ $
(You could simplify it by using an if, but I dig case-based maintainer
scripts)
> The -dev package must depend on the main package
And almost certainly on libc6-dev.
--
James
~Yawn And Walk North~
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
