Subject: Re: buildlink3 and /usr/lib (was Re: CVS commit: pkgsrc)
To: Jeremy C. Reed <firstname.lastname@example.org>
From: Johnny C. Lam <jlam@NetBSD.org>
Date: 08/06/2004 19:08:08
On Fri, Aug 06, 2004 at 10:11:11AM -0700, Jeremy C. Reed wrote:
> On Fri, 6 Aug 2004, Johnny C. Lam wrote:
> > Log Message:
> > Clear up a common misconception about buildlink3. The reality is that
> > everything in /usr/include and /usr/lib (system header and library
> > paths) is always considered part of the package build environment;
> > buildlink3 only isolates package builds from everything outside of
> > those system paths. As a consequence of this, LOCALBASE == "/usr"
> > effectively makes buildlink3 do nothing.
> Thank you for improving Packages.txt to further explain this.
> My main problem occurs even when I use default LOCALBASE as /usr/pkg. This
> is when I use one build system that detects alsalibs or some curses and
> then I try to use the packages on another system that doesn't have the
> alsalibs or has a different ABI for other libraries. alsa libraries (like
> libasound) is an example of something that pkgsrc doesn't provide yet (it
> is in pkgsrc-wip).
Right. We currently have a abstraction layer revolving around OS
detection, but OS detection isn't actually what we want. We really
want feature-detection, and the various builtin.mk files are a stab
at getting us there, but we're still far from that goal. I will try
to improve the documentation for writing builtin.mk files.
-- Johnny Lam <jlam@NetBSD.org>