Re: Pulling in python from a buildlink3.mk file

[Joerg Sonnenberger <joerg%britannica.bec.de@localhost>]

On Tue, Jan 26, 2016 at 11:10:13AM +0000, Martijn van Buul wrote:
> * Joerg Sonnenberger:
> > On Tue, Jan 26, 2016 at 07:37:58AM +0000, Martijn van Buul wrote:
> >> 
> >> I'm open to suggestions, but this is an oddball python package. It's
> >> not an egg, it's not a python binding for an existing C library; it's a
> >> C library which happens to use python internally as an extension
> >> language. 
> >
> > In that case, don't mess with the Python version?
> 
> You mean "Just pull in a specific version of python using it's normal
> buildlink3.mk file, and stick with that"? I hadn't thought of that; I was
> trying to do it "neatly", but if there is no neat and correct way it might
> best.

If you really need to expose it via b3.mk at all, ask the package which
version it was built against and pull the specific version's b3.mk in.

Joerg