[Proj] Coming releases of PROJ.4

[Sebastiaan Couwenberg]

On 06/23/2017 01:32 PM, Kristian Evers wrote:
>> In Debian embedded copy copies are not used, the packaged dependencies
>> are used in stead.
> 
> Okay. Out of curiosity, how do you make sure that it works? Potentially packages can embed conflicting versions,  I guess. Which might be the entire reason they embedded it in the first place. 

Test suites or manual testing mostly.

Because we don't want to patch all copies of a library for (security)
bugs, using embedded copies should not be done in Debian. Stripping the
embedded copy from the source is optional, so the presence of the code
does not imply that its used for the build.

Other reasons to embed code copies is to ease their build and deployment
on Windows, or to not need to a separate action to download the dependency.

As the maintainer of the proj package in Debian I say that anyone using
an embedded copy of PROJ.4 instead of building with the proj package
should be taken behind the barn and shot.

>> Searching for '#include [<"]projects.h[>"]' results in:
> 
> Still a list of around 10 projects. Not a huge impact in my mind. Does the Debian search tools have a way of determing the use of those packages? Download numbers or something like that?

There is popcon.debian.org to show how many systems (with popcon
reporting explicitly enabled) have the package installed and actually
user it (vote).

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1