| Summary: | Allow LIB_DEPENDS depend on ports with USE_LDCONFIG != yes | ||
|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Jan Beich <jbeich> |
| Component: | Ports Framework | Assignee: | Port Management Team <portmgr> |
| Status: | Closed Feedback Timeout | ||
| Severity: | Affects Only Me | CC: | jaap |
| Priority: | --- | Keywords: | feature, needs-patch |
| Version: | Latest | ||
| Hardware: | Any | ||
| OS: | Any | ||
Could you provide a patch that makes it valid so that it can be tested ? What's wrong with comment 0 rationale? Don't close an issue just because it lacks a patch. I haven't come up with one as LIB_DEPENDS code is fragile and this is low priority. I don't want to hurt feeling or such, but it looks like it needs a one line patch to bsd.sanity.mk, if nobody had time to do it in the 10 months the PR had been opened there's no point in keeping it opened. |
When a port defines USE_LDCONFIG != yes its consumers cannot use LIB_DEPENDS because it may match different library. LIB_DEPENDS = libfoo.so:${PORTSDIR}/bar/foo1 vs. LIB_DEPENDS = libfoo.so:${PORTSDIR}/bar/foo2 One could prepend ldconfig prefix # if USE_LDCONFIG = ${PREFIX}/lib/foo2 LIB_DEPENDS = foo2/libfoo.so:${PORTSDIR}/bar/foo2. $ make depends ===> test-0.1 depends on shared library: foo2/libfoo.so - found (/usr/local/lib/foo2/libportaudio.so.0) except portlint and bsd.sanity.mk claim it's illegal. Workarounds include using soversion if different, renaming library, explicit BUILD/RUN_DEPENDS or doing nothing. Is this a sane idea?