[macports-ports] 01/02: xml-security-c: update to 2.0.0

[Ryan Schmidt]

On Jul 13, 2018, at 21:33, Jeremy L wrote:

> On 07/05/2018 01:29 AM, Ryan Schmidt wrote:
>> On Jul 4, 2018, at 14:07, Jeremy L wrote:
>>> Jeremy L (nerdling) pushed a commit to branch master
>>> in repository macports-ports.
>>> 
>>> 
>>> https://github.com/macports/macports-ports/commit/0ef87ed1231742cf86a026814f6e866fef4268db
>>> 
>>> commit 0ef87ed1231742cf86a026814f6e866fef4268db
>>> 
>>> Author: Jeremy Lavergne
>>> AuthorDate: Wed Jul 4 14:54:28 2018 -0400
>>> 
>>> 
>>>     xml-security-c: update to 2.0.0
>> The library version has increased from 17 to 20. There are three ports that declare a dependency on this port. Do any of them link with the library? If so, their revisions need to be increased to rebuild them.
>>> -depends_lib         port:xercesc3 path:lib/libssl.dylib:openssl
>>> +depends_lib         port:xercesc3 path:lib/libssl.dylib:openssl port:pkgconfig
>> Does it really use pkgconfig at runtime?
> 
> These sound like good candidates for lint/tests :-)

In the case of the first issue, "lint" has no knowledge of previous versions of the Portfile, and it has no knowledge of what files the port installs. There is no way "lint" can help you know when you need to increase the revision of dependencies. You need to pay attention to that sort of thing yourself.

For the second issue, yes, "lint" could issue a warning when certain ports that are commonly used as build dependencies are possibly inadvertently listed as non-build dependencies. However this would result in false warnings in those few ports that have a legitimate reason to declare a non-build dependency on one of those ports. For example, ImageMagick declares a library dependency on pkgconfig, because it uses it at build time to find its dependencies, and it also uses it at runtime if you use the Magick-config script. This is fairly unusual though so it would not be unreasonable to add this warning.