Package: dpkg Version: 1.14.19 Severity: normal Hi all,
Right now, if you have two packages that have a relationship with each other beyond a strict Dependency, there is no way to communicate that relationship to dpkg. I'm talking about things covered semantically by the Should-Start field of the LSB init scripts and things like that. There are several package sets in the archive where A does not Depend on B, but needs to have it's postinst run after B in certain circumstances. It would be great if we had a new field in debian/control for something semantically equivalent to Should-Start or configure-before. Thanks, -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8) Shell: /bin/sh linked to /bin/dash Versions of packages dpkg depends on: ii coreutils 6.10-6 The GNU core utilities ii libc6 2.7-11 GNU C Library: Shared libraries dpkg recommends no packages. -- no debconf information -- ----------------------------------------------------------------- | ,''`. Stephen Gran | | : :' : [EMAIL PROTECTED] | | `. `' Debian user, admin, and developer | | `- http://www.debian.org | ----------------------------------------------------------------- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
