subversion uses libproxy without declaring dependency

[ryandesign (Ryan Carsten Schmidt)]

I must've had libproxy installed when I installed subversion. Then I uninstalled libproxy via port_cutleaves. Now trying to use svn points out:

dyld: Library not loaded: /opt/local/lib/libproxy.0.dylib
  Referenced from: /opt/local/bin/svn
  Reason: image not found

subversion should either declare a dependency on libproxy or should not use libproxy.

[danielluke (Daniel J. Luke)]

Did it perhaps pick it up via neon? I'm not seeing where subversion would directly use libproxy...

Can you run /opt/local/bin/neon-config --libs and paste the output here?

[ryandesign (Ryan Carsten Schmidt)]

I think you're right that it's neon's issue:

$ /opt/local/bin/neon-config --libs
-L/opt/local/lib -L/opt/local/lib -lneon -lintl -lz -L/opt/local/lib -lssl -lcrypto -lz -dynamic -O2 -Wl,-search_paths_first -lgssapi_krb5 -lkrb5 -lk5crypto -lcom_err -lresolv -L/opt/local/lib -lproxy -lexpat

If neon is changed to no longer use libproxy, subversion will still need a revbump, since (regardless of reason) svn is linked with libproxy.

[danielluke (Daniel J. Luke)]

r63552 for neon change.

subversion revbump in r63554