On Tue, Jan 04, 2011 at 11:21:24PM +0100, Philipp Schafft wrote:
I added a debconf question asking if the package should be configured.
Choice is good, but not what this bug is about.This bug is about default behaviour. So only if default config (with or without interacting with debconf!) is to _not_ enable DECnet, this bug is not solved by that approach.
I'm not going to change the recommends to suggests as suggests is much to weak and will affect other users ('why is my network net set up correctly?').
Users of DECnet obviously need DECnet configured by default. My proposal is not to change that.
But users of DECnet should install the _tool_ to handle DECnet, not just install the _library_ and expect that to pull in the tool. That is simply the wrong way around, and cause this bugreport: Currently users of _any_ tool which _can_ support DECnet, gets DECnet enabled by default.
No user of the _library_ should be surprised that it did not magically setup their network!
Users of the tool should be unaffected by the change of the _libary_ no longer pulling in the tool. After all, users of the tool should explicitly install the tool!
I strongly believe that the simplest and most elegant approach to solving this bug is to lower the relationship of the _library_ with the _tool_ to only be a suggestion.
Hope that helps, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: Digital signature
