On Tue, Nov 12, 2013 at 10:10:58PM +0100, Victor Seva wrote: > Hi Steve,
> Thanks for your quick reply. > 2013/11/12 Steve Langasek <[email protected]>: > > If, however, you are enabling the tls plugin *by default* - for > > instance, by providing a metapackage that pulls the two separate packages in > > together, or by having a Recommends: that automatically pulls the tls module > > in and automatically activates it > Ok. But in this case installing the module *by default* via Recommends > will *not* get the module active nor loaded. > The user has to change the default configuration file and explicitly > activate the tls module in order to get the tls loaded. > Is is then ok to have the tls module in Recommneds? In that case, yes: because combining the plugin into a single program is an action taken by the user (by modifying the config), not by the maintainer. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ [email protected] [email protected]
signature.asc
Description: Digital signature
