Subject: Re: python makefile stuff
To: Johnny C. Lam <firstname.lastname@example.org>
From: David Brownlee <email@example.com>
Date: 05/08/2001 10:50:05
How about a mk/pkg.python.mk which could be included by individual
David/absolute -- www.netbsd.org: No hype required --
On Mon, 7 May 2001, Johnny C. Lam wrote:
> Murray Armfield <firstname.lastname@example.org> writes:
> > Hi folks,
> > Just a quickie; is there any effort / interest in moving the
> > python makefile include stuff from lang/python/Makefile.inc to bsd.pkg.mk?
> I don't believe so. It's not hard to include
> ../../lang/python/Makefile.inc in your own packages, and changes to
> just this one file won't affect all other packages as it would if the
> changes had to be made to bsd.pkg.mk. The perl5 code was integrated
> into bsd.pkg.mk, but if I had to do it again, I'd separate it out into
> a new file to be included by p5-module packages.
> > Currently I use my own pkgsrc area as well as NetBSD's but for python
> > dependancies I need a copy of this Makefile.inc as well as bsd.pkg.mk. Can it
> > be consolidated?
> I face similar problems when I work on new php4 packages. I generally
> just make symlinks from /usr/pkgsrc/mk and /usr/pkgsrc/www/php4 into
> my local pkgsrc tree and all my problems are solved.
> -- Johnny C. Lam <email@example.com>
> Department of Statistics, Carnegie Mellon University