Bug#165921: libc6: Please use debconf to warn of likely breakage on major upgrade
On Thu, Nov 07, 2002 at 02:08:27PM -0500, Ben Collins wrote:
> Sorry, We cannot make libc6 depend on debconf. That would make
> debconf more essential than libc6. You can see the circular dep
> problem.
Ah yes, I hadn't thought it through ... but for options or notes which
are not critical to libc6's operation, could debconf be used
opportunistically?
For example, would the presence of a 'templates' control file warning
of the JDK breakage do any harm if it were not picked up by debconf?
Obviously this is extra work, and extra complication in something
which is already complicated. Could the debconf stuff be put in a
separate package ("libc6-familiar"?) with a tight dependency on libc6
version, and a Suggests: in the opposite direction?
Of course this is getting a little close to "Ooh, I see you're
upgrading your shared C library. Would you like me to a) stuff it up
for you, or b) leave you to get on with it ?".
Matthew #8-)
Reply to: