2012/1/19 Manuel A. Fernandez Montecelo <manuel.montez...@gmail.com>: > [...] > This is not fixed yet, but I am unconvinced about the utility of such > script and if it was for me I would remove it altogether, as I did > with other ad-hoc script in the package which was not even shipped. I > will probably do that in 1.8. > > The whole point of a plugin is that your application doesn't have to > use all of the features provided by software, and plugins are optional > features. So IMO it doesn't make sense to provide such file so > packagers of other Debian software point to it and load all of the > plugins (even if they don't cause runtime overhead, which hopefully > they will not). It's up to the applications to decide what they use.
Adding another comment from upstream, OGRE's CMake/Linux guy: "Most applications probably do ship their own version of plugins.cfg (after all, no other platform offers a default plugins.cfg to rely on). Loaded but unused plugins will incur a slight memory penalty, but shouldn't otherwise affect performance." So even if no harmful (well, actually they're now creating problems for the issue at hand), the way that Debian packages handle this is ad-hoc and different from OGRE community practice. I think that it should be removed in the future. Regards. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
