Sebastian Rittau <email@example.com> writes: > On Sun, Jul 13, 2003 at 01:51:07PM +1000, Ben Burton wrote: > >> It seems then that our options are as follows. >> >> (i) Wait for the Qt maintainers to upload a fix. >> (ii) Do an NMU for Qt, despite the fact that this bug is not release-critical. >> (iii) Resort to the technical committee. >> (iv) Keep the package split and release sarge with a broken Qt development >> environment. > > Option (iii) is certainly the way to go. Problems like this are exactly > what the TC is for. > > My suggestion: Add a "Recommends: libqt3-compat-headers" to libqt3-dev. > A dependency is too strong, since libqt3-dev is perfectly usable without > the compatibility headers, but a recommendation ensures that the compat > headers are installed along libqt3-dev in most cases. Uhh, there's no reason the compat headers should have been split out in the first place. -- Poems... always a sign of pretentious inner turmoil.
Description: PGP signature