Subject: Re: tools.mk, USE_GNU_TOOLS=yacc and _TOOLS_REPLACE_OPSYS
To: None <tech-pkg@NetBSD.org>
From: Bruce J.A. Nourish <email@example.com>
Date: 03/10/2004 07:47:56
On Tue, Mar 09, 2004 at 11:18:49PM -0700, Bruce J.A. Nourish wrote:
> On Tue, Mar 09, 2004 at 08:44:45PM -0800, Jeremy C. Reed wrote:
> > Who uses Linux here?
[replying to the multitude of posters on this thread]
Everyone else who answered seems to have done so on the basis that
the base system is all that is installed. Such a system would not
have most of these tools; it wouldn't have a C compiler either.
Surely we are assuming a certain amount of cluefulness on the part
of the user?
I think the best solution is to require the user to have these tools
before starting to use pkgsrc. Hacking bootsrap-pkgsrc is a crap
solution because binary bootstrap kits don't use the build script.
Perhaps a more general solution would be to write a pkgtool that
checked the non-pkgsrc available tools and decided intelligently
if they were acceptable. The defs.$OPSYS.mk files would become
fallbacks in case the user chose not to run such a tool. Maybe on
non-standardized platforms, the use of this tool would be mandatory?
Bruce J.A. Nourish <firstname.lastname@example.org> http://bjan.freeshell.org
SDF Public Access UNIX System - http://sdf.lonestar.org