[72523] trunk/dports/net

[Ryan Schmidt]

On Oct 19, 2010, at 14:19, Anders F Björklund wrote:

> Ryan Schmidt wrote:
> 
>>>>> +checksums	md5 adfd092d7cd45c9797105e433662591f
>>>> 
>>>> Should use multiple checksums.
>>> 
>>> From the macports svn ? I suppose it could, but...
>> 
>> I think it's a security measure we want every port to exemplify.
> 
> And you still want to use both sha1/rmd160 rather
> than just sha256, right ? (In addition to the md5.)

As I update ports I have been using sha1 and rmd160 only. I've been removing md5 on the theory that it is obsolete and needn't be used for anything anymore, and sha256 is not yet in a released version of MacPorts.


>>>>> +depends_lib	lib:libfetch.5:libfetch lib:ssl:openssl
>>>> 
>>>> Should use port:-style dependencies.
>>> 
>>> What is wrong with library (lib) dependencies ?
>> 
>> A library the user installed in another location without using MacPorts could satisfy the dependency, but we don't want that to be possible.
> 
> So how do you encode the version in a port: depends ?

You can't. Anyway that was another problem with lib:-style dependencies: the need to track dependencies' library version numbers.

> Just trust that everything is upgraded automatically ?

Yes, which it is.

> Seems like there is an error in the dependency anyway.
> Supposed to be "fetch.5" rather than "libfetch.5"...

No, libfetch.5 was right since the port does install a file "libfetch.5.dylib".


> And lib:ssl:openssl installed openssl @1.0.0a_0 anyway,
> even though /usr/lib/libssl.dylib was also available.

That's because there was no file called "ssl.dylib"; if you wanted to allow a file "libssl.dylib" the dependency would have had to be "lib:libssl:openssl".

See:

http://guide.macports.org/#reference.dependencies.types