On Thu, Apr 24, 2014 at 21:24:17 +0200, Magnus Holmgren wrote: > tisdagen den 22 april 2014 22.12.24 skrev Steve M. Robbins: > > I think I understand the rationale for using the super-fine-grained symbol > > versioning. If someone from the debian-science-maintainers team would like > > to maintain this file, please go ahead and commit it to the repository. > > Unfortunately, I don't have the time to audit each release; so if left to > > me, I will use the easy and conservative "dh_makeshlibs -V" solution. > > Once the symbols file is in place, maintaining it shouldn't require very much > effort. As I explained, dpkg-gensymbols, which is run by dh_makeshlibs, tells > you about any symbol changes when you build the package. You merely have to > apply the generated diff to the symbols file and adjust the minium required > version appropriately, making the procedure more automated compared to > manually checking when the dependencies have to change. Running simply > "dh_makeshlibs -V" should be avoided as will result in unnecessarily tight > dependencies and therefore may delay testing transitioning. > More importantly, a symbols file lets you detect when symbols go away. dh_makeshlibs -V doesn't do that.
Cheers, Julien
signature.asc
Description: Digital signature
