Subject: Re: pkg/13649: print/gv needs updating for "buildlink.mk"
To: Johnny C. Lam <lamj@stat.cmu.edu>
From: Greg A. Woods <woods@weird.com>
List: netbsd-bugs
Date: 08/07/2001 23:17:38
[ On Tuesday, August 7, 2001 at 18:47:55 (-0400), Johnny C. Lam wrote: ]
> Subject: Re: pkg/13649: print/gv needs updating for "buildlink.mk" 
>
> That doesn't sound right and would point to a bug in xpkgwedge, no in
> print/gv.  Since gv uses imake to generate its Makefile, there is
> something wrong with the Makefile generation caused by xpkgwedge's
> presence.

In fact I don't want xpkgwedge to affect where a package finds
*third-party* packages -- only where the package itself installs!
Anything more would be wrong!

If it does any more then it is broken and will cause the same breakages
that buildlink.mk files are supposed to avoid.  It makes no sense
whatsoever to use BUILDLINK only on non-imake packages since that'll
leave imake-using packages with the problems now eliminated in packages
using BUILDLINK!

> That will break many more packages than just print/gv, as most
> packages rely on finding libraries and headers under ${LOCALBASE}.
> Only the small (but growing!) collection of packages a few of us have
> been "buildlinkifying" don't assume the presence of libraries and
> headers in the installation tree.

I really do want to break the packages that are not yet using BUILDLINK
since I'm only using binary packages on the final production machines.

I do not ever want any packages to find libraries or headers of other
packages under $PREFIX while they're building.

I want to avoid as many of the headaches with third-party libraries as I
can this time around, especially with the ugly shared ones.  If that
means I have to convert packages to using BUILDLINK as I need then
that's fine -- I'm happy to do that!  I'm only using a very tiny subset
of all of pkgsrc anyway (about 150 or so total last time around)....

> Could you show me what you have in /etc/mk.conf that makes your pkgsrc
> builds effectively non-standard?  It sounds like you've been working
> on the same problem that buildlink was invented to solve, and it would
> be beneficial to compare methods.

No, I've not been doing very much different with packages lately.  I've
brought forward my hack on some minor stuff to resurrect and fix the
REQUIRE files, etc., and I've got some minor tweaks to handle calling
"make package" with "su" (just like "make install" does), as well as a
couple of itty bitty fixes and improvements.

I'll send you my pkgsrc/mk/* diffs, and a sample mk.conf directly so
that they don't clog up this PR.

-- 
							Greg A. Woods

+1 416 218-0098      VE3TCP      <gwoods@acm.org>     <woods@robohack.ca>
Planix, Inc. <woods@planix.com>;   Secrets of the Weird <woods@weird.com>