I agree that we should ship plugins if they can build without the
dependencies being present, as long as they are disabled in the user
interface until the user installs the needed dependency.  This way
users can add the feature if they want to build the dependency
themselves without needing to rebuild the plugins.

If the plugin causes the UI to show a feature that is not supported,
then we should either fix that or not ship the plugin for now.

Brian


On 02/04/10 14:10, Nicolas Williams wrote:
> On Thu, Feb 04, 2010 at 12:17:38PM +0800, Jeff Cai wrote:
>>           - Instant Message (Gajim)
>>             Gajim is not integrated in OpenSolaris, so the Gajim plugin
>>             is not delivered.
>
> But does the plug-in for sending to Gajim depend on Gajim in order to
> build?  If not, I'd say "deliver it", because Gajim is in /contrib -- if
> it all Just Works when you install Gajim from /contrib (or build it
> yourself), well, that's a good thing.  OTOH, if you have no way to test
> this plugin, and don't have the resources to integrate Gajim, then
> excluding the plugin makes sense.
>
>>             Like Pidgin, the Gajim "Send as" item only appears when gajim
>>             is running. The "Send to" drop down list is generated by querying
>>             online buddies through Gajim D-Bus method calls.
>>
>>             nautilus-sendto calls the D-Bus method "send_file" to do the 
>> actual
>>             sending action.
>
> By the sounds of it, this plugin depends only on D-Bus interfaces of
> Gajim, so you can build it without Gajim being installed, correct?
>
> The same logic applies to other plugins, IMO.
>
> Nico

Reply via email to