Debconf or not debconf : Conclusion

[Julien LEMOINE <speedblue@debian.org>]

Hello,

	First of all, I present my excuses for having started a new debate
about debconf in debian-devel.
	
	Secondly, to reply to every person who thinks I should have created a 
more "user friendly" migration who did not break backwards compatibility. 
My answer is that I have no time to implement command line support for 
stunnel 4.x.

	Finally, since there is not really a policy about when to use debconf, 
I will respect the DFSG [1] and add a debconf warning [2] in the 
stunnel package.

Thanks for all your comments.
Best Regards.

[1] "4. Our Priorities are Our Users and Free Software "
[2] Description: general notes about stunnel
 * stunnel 4.x does not support any more command line arguments, so you need
   to edit /etc/stunnel.conf by hand if you are upgrading from stunnel 3.x
 * For stunnel versions >= 4.04-4, the file /etc/default/stunnel 
   is provided and you need to set ENABLED=1 to allow stunnel to be 
   started from init.d
 * To set up stunnel for server use, read the 
   /usr/share/doc/stunnel/README.Debian file.

-- 
Julien LEMOINE / SpeedBlue