RE: plugins

> > applications above becomes an LSB certified App, I can 
> > begin to rely on the behavior of the app remaining consistent
> > across all Linux distributions. So if I make a plugin for it, 
> > the plugin goes in /opt/whetever.../plugins. All the time. 
> > End of story. The plugin writer is not concerned directly with the
LSB.
> 
> Just to make a point here about the FHS and addons/plugins to 
> a product described above.
> 
> The /opt/whatever..../ directory would most likely be a
> /opt/<provider>/package hiearchy and as such if the provider has
> registered their /opt/provider path with LANANA, the ../plugins
> directory may pose a problem as only the provider should be able
> to add items into this directory path. Plugins by others would
> not normally be allowed to go here. If you, as someone other than
> the "provider" wanted to place something there it would not be
> LSB conformant.
> 
> So to the statement of "The plugin writer is not concerned 
> directly with the LSB." the plugin developer should be concerned
> as they would be violating the specification.

Doug, can I ask you to file a report on this in our bugtracker?
I think we just turned over a rock we didn't look under before,
and need to remind ourselves to think about wording for this.