Short description don't report all necessary information. Reproducible: Always Steps to Reproduce: equery u abiword | grep plugins Actual Results: plugins : Enable plugins build Expected Results: Something like: plugins : Enable plugins build (includes support of the .odt format)
It enable support for plugins, loading, building, ... The fact that it enables a list of plugins by default would take too much place to list them all.
(In reply to comment #1) > It enable support for plugins, loading, building, ... The fact that it enables > a list of plugins by default would take too much place to list them all. > Yes, It is. But this USE also includes build of some plugins (the first and the main one is the plugin for support the Open Document Format). And another unpleasant surprise is the fact, that the default configuration of AbiWord doesn't include the support of .odt-files. I think, that the description of USE flags of app-office/abiword should contain some info about actions, needed to include support of ODT format.
If you take a look at: src_configure() { local plugins="" if use plugins; then # Plugins depending on libgsf plugins="t602 docbook clarisworks wml kword hancom openwriter pdf loadbindings mswrite garble pdb applix opendocument sdw xslfo" # Plugins not depending on anything plugins="${plugins} gimp bmp freetranslation iscii s5 babelfish opml eml wikipedia gdict passepartout google presentation urldict hrtext mif" # inter7eps: eps.h # libtidy: gsf + tidy.h # paint: windows only ? use collab && plugins="${plugins} collab" use gnome && plugins="${plugins} goffice" use latex && plugins="${plugins} latex" use libgda && plugins="${plugins} gda" use math && plugins="${plugins} mathview" use openxml && plugins="${plugins} openxml" use ots && plugins="${plugins} ots" # psion: >=psiconv-0.9.4 use readline && plugins="${plugins} command" # plugin doesn't build #use svg && plugins="${plugins} rsvg" use thesaurus && plugins="${plugins} aiksaurus" use wmf && plugins="${plugins} wmf" # wordperfect: >=wpd-0.8 >=wps-0.1 use wordperfect && plugins="${plugins} wpg" fi gnome2_src_configure --enable-plugins="$(echo ${plugins})" } You will see there are a lot of plugins, then, I think current description is the best we can do since opendocument plugin cannot be considered as "the most important one". (In reply to comment #2) > And another unpleasant surprise is the fact, that the default configuration of > AbiWord doesn't include the support of .odt-files. For this we could probably enable "plugins" USE flag by default, but I don't know what other team members think :-/
for the record, I've been exploring the possibility of splitting plugins again. It seems most (if not all) plugins can be built out of a built abiword source tree which would result in pretty much what the situation was with earlier releases.
(In reply to comment #3) > > And another unpleasant surprise is the fact, that the default configuration of > > AbiWord doesn't include the support of .odt-files. > > For this we could probably enable "plugins" USE flag by default, but I don't > know what other team members think :-/ > AFAIR the Open Document Text is the basic OpenSource text processor format. So, to my mind, it's support should be included independently on any USE flags. In this case I think it will be right just to ask other team members about what they think about this idea (that ODT-support plugin should be included in base configuration of the AbiWord). ;)
+ 04 Feb 2011; Pacho Ramos <pacho@gentoo.org> metadata.xml: + Give more information about 'plugins' USE flag. + It now says the following: <flag name='plugins'>Enable plugins build (see http://www.abisource.com/wiki/PluginMatrix for more information). If your file cannot be opened due lack of support, try enabling this.</flag>
