Re: freetype: incorrect shlibs file generation
On Thursday, 21 December 2017 11:53 PM, Cyril Brulebois wrote:
> Yeah, that would look good to me, provided there's nothing added in a
> x.y.z version that would make the udeb depend on x.y (in the metadata
> section) while it actually depends on a feature introduced in a x.y.z
> (on a shared object level).
This shouldn't happen, since freetype uses x.y.z as major.minor.patch.
So a release incrementing z should only fix bugs, not alter the API.
> FWIW dh_makeshlibs supports being called with a -V option. Excerpt of
> its manpage:
> That might be a safer approach?
Yes, but it is conservative, perhaps. 'dh_makeshlibs -V' then depends on 2.8.1.
Given what we know about freetype's versioning, this doesn't seem necessary IMO.
On another note, I was wondering if using 'cut' is simpler than 'sed'?
$(shell echo "$(ver)" | cut -f-2 -d'.')