On Thu, Jan 05, 2017 at 12:44:52PM +0000, Stuart Henderson wrote:
> On 2017/01/05 13:40, Landry Breuil wrote:
> > On Thu, Jan 05, 2017 at 01:28:06PM +0100, Alexander Bluhm wrote:
> > >
> > > > You will also need to bump REVISION in x11/gnome/builder/Makefile (it
> > > > has a library dependency on devel/llvm for libclang.so).
> > >
> > > I have not bumped llvm-main as the package should not change. And
> > > llvm-python is new, so it also has no revision. As x11/gnome/builder
> > > depends on the unchanged llvm-main, it should not require a bump.
> > > Did I miss something?
> >
> > I might be wrong, but the pkgpath for a port is registered in the
> > PLISTDB (@comment, 3rd line) and in the installed package ( grep pkgpath
> > /var/db/pkg/llvm*/+CONTENTS) , so if you change the pkgpath for llvm
> > 'main' (as you do, going from devel/llvm to devel/llvm,-main), PLISTDB
> > or pkg_add *should* complain if you dont bump.
>
> Correct; you'll need to bump llvm's REVISION-main as well as x11/gnome/builder
> then.
>
> On 2017/01/05 13:28, Alexander Bluhm wrote:
> > Somehow I can uninstall llvm although py-llvm should depend on it.
> > Should llvm appear in the signature of py-llvm? Does
> > LIB_DEPENDS-python=${BUILD_PKGPATH},-main not work as expected?
>
> For the LIB_DEPENDS to be registered you need an entry in WANTLIB for
> a library from that package. The best idea is probably to set
> "WANTLIB-python=clang". (Python modules often dlopen their libraries
> so they don't show up anywhere that port-lib-depends-check can find
> them).
Hmm, but is it a real WANTLIB, what does port-lib-depends-check have to say
about it?
Or maybe just a RUN_DEPENDS?
RUN_DEPENDS-python = ${BASE_PKGPATH},-main=${LLVM_V}
--
Antoine
