Hi Slawek, On Wed, Jun 01, 2011, Slawomir Bochenski wrote: > > Aren't most/all plugins compiled as built-in and all built-in plugins > > loaded by default? Then you shouldn't need to provide any -p option to > > get everything loaded. If this is the case could you update your patch > > to simply remove the --ftp and --opp options without adding the --plugin > > option. > > > > Johan > > > > This was specifically made for retaining original behaviour. Simply > removing --ftp and --opp would make obexd load all available plugins, > which isn't how this worked until now. I don't think the content of the default .service file has been thought out so deeply, so I wouldn't put too much effort into retaining the *exact* same behavior as before. Distros will typically customize it anyway for their needs. What does make sense though is to have some kind of sensible defaults there. Aren't all plugins a sensible default? Do we have something inherently unstable/experimental that could mess up systems? If so then that should probably be disabled by default already at configure time, and if you really want to have something in the service file it's probably easier to use -P instead of -p since the "bad" plugins are in the minority. Johan -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
