Revert r261296. This removes the WITHOUT_NCURSESW option.

It was the wrong direction. We will instead remove use of the
non-wide-character supporting libncurses.

Use src.opts.mk in preference to bsd.own.mk except where we need stuff
from the latter.

Merge from CheriBSD:
commit c1acf022c533c5ae27e0cd556977eafe3f5959eb
Author: Brooks Davis <brooks@one-eyed-alien.net>
Date: Fri Jan 17 21:46:44 2014 +0000

Add an option WITHOUT_NCURSESW to sup

Merge from CheriBSD:
commit c1acf022c533c5ae27e0cd556977eafe3f5959eb
Author: Brooks Davis <brooks@one-eyed-alien.net>
Date: Fri Jan 17 21:46:44 2014 +0000

Add an option WITHOUT_NCURSESW to suppress building and linking to
libncursesw. While wide character support it useful we'd like to
only need one ncurses library on embedded systems.

MFC after: 4 weeks
Sponsored by: DARPA, AFRL

show more ...

Build usr.bin/ with WARNS=6 by default.

Also add some missing $FreeBSD$ to keep svn happy.

Replaced afterinstall: with equivalent FILES and SYMLINKS.

Fixed style of DPADD and LDADD assignments as per style.Makefile(5).

FIx catalog name I overlook in prev. obsolete locales removing

Submitted by: ru

Remove deprecated locale names

Unifdef has got some crack-smoking exit values:
"The unifdef utility exits 0 if the output is an exact copy of the input,
1 if not, and 2 if in trouble."

This causes an 'Error code 1 (ignored

Unifdef has got some crack-smoking exit values:
"The unifdef utility exits 0 if the output is an exact copy of the input,
1 if not, and 2 if in trouble."

This causes an 'Error code 1 (ignored)' in the world output, which upsets
the whereintheworld scripts that the tinderboxes use.

However, this stuff here is a relic. We do not enable HAVE_TCL_INTERP
nor HAVE_PERL_INTERP.. The Makefile hooks to turn them on have gone ages
ago, and this stuff was here for release building purposes only. Rather
than fight with the tinderbox builds, clean house a bit and remove the
last remaining unused relics of this stuff.

show more ...

Drop support for COPY, -c has been the default mode of install(1)
for a long time now.

Approved by: bde

s/${INSTALL} -c/${INSTALL} ${COPY}/

Remove Perl and TCL/TK bits, neither of which are in the base system
(anymore).

Remove NO_WERRORs and WARNS=n's. To be revisited after GCC3.

Protect this against the to-come WARNS=2 default.

Style fix: use .else where appropriate.

PR: 29489
Submitted by: Joseph Mallett <jmallett@xMach.org>

Add more *.US-ASCII entries

Understand new locale names and Latin15

Drop support for -DRELEASE_BUILD_FIXIT and -DCRUNCHED_BINARY in
${CFLAGS}. The only supported method thus is -DRELEASE_CRUNCH.

MAN[1-9] -> MAN.

Install Ukrainian message catalog.

Perl support in vi is broken if perl has thread support built in.
Document this. Minor nitpick in other comments.

We're using ncurses now.

$Id$ -> $FreeBSD$

The perlinterp option builds and works, but I'm not so sure how it'll go
in a release or buildworld environment, so I'll leave it disabled.

Remove tcl from /usr/src, according to prior agreement. BTW, tcl-8.0 *is*
a port so there is nothing to be done on that side now.

Approved by: jkh
===
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
c

Remove tcl from /usr/src, according to prior agreement. BTW, tcl-8.0 *is*
a port so there is nothing to be done on that side now.

Approved by: jkh
===
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
cc: Andreas Klemm <andreas@klemm.gtn.com>, current@freebsd.org
Subject: Re: Make this a relese coordinator decision (was Re: ports-current/packages-current discontinued)
From: David Greenman <dg@root.com>
Date: Sun, 03 Aug 1997 20:23:31 -0700

>decision is, I'll respect it.

Another chance to architect people's principles...I can hardly wait. Seems
quite appropriate for a Sunday - I just need to get one of those collection
plates (and money envelopes) so I can profit, too. :-)
Tcl stays in /usr/src for now, but it needs to be kept up to date; same
for perl. If Jordan doesn't have "setup" (written in tcl) ready for 3.0,
then tcl will be yanked prior to the 3.0 release (and made into a port).
As for the ports tree only supporting the last FreeBSD release, this seems
sensible to me. The "ports" have always been a moving target between releases
and the problem is only going to get worse when we expand to supporting other
processor architectures. In any case, Satoshi is and always has been in charge
of the ports tree and whatever he wants to do with it (within reason :-)) is
his decision.
Does this cover the issue completely? I admit to deleting messages in this
thread with unusual fervor (people have FAR too much time on their hands!).
There's a fair bit of reasoning behind the above, but since everyone is sick
of arguing about this, I'll spare you the analysis.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project

show more ...