Re: test for curses before bootstrap

[Brandon Bergren <bdragon%mailsnare.net@localhost>]

On Mon, 7 Jan 2008, David H. Gutteridge wrote:

> David Griffith wrote:
> > > Wouldn't it be a good idea to include a check for curses headers during
> > > bootstrap? I know its RTFM, but it may be non-trivial to track down why
> > > the bootstrap stoped.
> > >
> > > Something like this:
> > >
> > >   echo_msg "Looking for curses header files"
> > >   if [ ! -f /usr/include/curses.h ] || [ ! -f /usr/include/ncurses.h ]; 
> > > then
> > >           die "You need curses header files to bootsrap pkgsrc (see 
> > > README.$opsys)"
> > >   fi
> >
> > Most Linux distros seem to have a default lack of a development headers,
> > so this sounds like a very good idea.
>
> I PRed this two years ago after experiencing a bootstrap failure:
> http://www.netbsd.org/cgi-bin/query-pr-single.pl?number=28926
> I included a patch in the PR but it (or something equivalent) hasn't
> been committed.
>
> Regards,
>
> Dave

Wait a second, bootstrapping requires curses?

I've been patching stuff locally to use mk/curses.buildlink3.mk for the 
past two years or so, as I don't want to have to maintain a system curses
on my slackware boxen.

Is curses support really *necessary* for any of the bootstrap tools?

--
> From the mailer of
|_|0|_| B R A N D O N     B E R G R E N
|_|_|0|  T e c h n i c a l
|0|0|0|   G e n e r a l i s t  ( C S )