On Sun, 21 Apr 2013 23:38:44 +0200 Christian Faulhammer <fa...@gentoo.org> wrote:
> the upcoming Claws Mail release will have no separation between > internal plugins (stuff that is built on mail-client/claws-mail with > USE="crypt bogofilter") and external ones (all packages > mail-client/claws-mail-*) anymore. > All are now integrated, which would mean 21 additional USE flags for > Claws or alternatively a new set of CLAWS_MAIL_PLUGINS which includes > the old and new internal plugins. > > Any objections against the addition? Wouldn't it be better to use the feature-intended USE flags and common sense to provide the users with best possible experience? Use proper USE flags for features which having switchable benefits user, and just enable others unconditionally (with USE=-minimal, maybe). This is, for example, how ekg2 ebuild does. It means that users need not to be aware of exact plugin structure, and the global USE flags help them in getting the features they expect. Since plugins can be enabled and disabled dynamically from within the program, they still have the full flexibility. For example, I'd expect USE=gpg to bring me the GPG encryption support, or USE=html to bring HTML message viewing support. Then we have flags to further narrow down the engine choice, like USE=webkit. Use them wisely and it will be much more helpful than claws_mail_plugin_gpg and claws_mail_plugin_fancy. -- Best regards, Michał Górny
signature.asc
Description: PGP signature
