Hello, 2011/12/30 Paul Wise <p...@debian.org>: > I suggest that you contact upstream to find out why they do not use > versioned names for the plugin-related files.
They plan to do that but in the long run along with other changes, probably it won't happen in the upcoming 1.8 series (which were planned to be released by now). I uploaded 1.7.3-5 yesterday with more changes regarding this: http://packages.debian.org/sid/amd64/libogre-1.7.3/filelist Plugins (for amd64) are now in: /usr/lib/x86_64-linux-gnu/OGRE-1.7.3/ I don't know if this is going to make users of the library very happy (for development or for games providing plugins.cfg with a fixed path), or they'll refrain from using Debian packages and install their own version. For our packages that will depend on OGRE it doesn't make any difference, but maybe the packagers have to do some extra work modifying the plugins.cfg provided from upstream. > Your solution sounds fine, I'm not sure if it will work for these: > > libogre-1.7.3: /usr/bin/update-ogre-plugins > libogre-1.7.3: /usr/share/man/man1/update-ogre-plugins.1.gz 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. Cheers. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
