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 ...

$@ is deprecated, use ${.TARGET} instead. Ditto for other single character
$n.
PR: conf/3273

Polish message catalogs for vi.

Submitted by: abial@warman.org.pl
PR: 4522

Fix 1.17 properly by adding ${DESTDIR} in front. (I know this part is
not enabled now.)

Drop the TCL hook for the time being until the tcl dust settles some more.

Fixed another make world stopper ;)
If TCLINTERP is defined, CFLAGS needs an additional include path:
-I/usr/include/tcl
Otherwise tcl.h can't be found during make world.

Enable GLOBAL tags support.

Oops. Broke golden rule #1: test everything before commit. :-]

Respect NOTCL, don't link with libtcl for the scripting support if
we're not building it.

Revert $FreeBSD$ to $Id$

Make the long-awaited change from $Id$ to $FreeBSD$

This will make a number of things easier in the future, as well as (finally!)
avoiding the Id-smashing problem which has plagued developers for so

Make the long-awaited change from $Id$ to $FreeBSD$

This will make a number of things easier in the future, as well as (finally!)
avoiding the Id-smashing problem which has plagued developers for so long.

Boy, I'm glad we're not using sup anymore. This update would have been
insane otherwise.

show more ...

Use ${COPY} instead of -c for installing non-source files.

When using the perl5 extensions, ask perl itself what the pathnames are,
don't just hard code them into the Makefile.

(This is the optional stuff to use perl scripts as a vi scripting language.
eg,

When using the perl5 extensions, ask perl itself what the pathnames are,
don't just hard code them into the Makefile.

(This is the optional stuff to use perl scripts as a vi scripting language.
eg, to load a sample script, type: :perl do 'wc.pl';
this loads /usr/share/vi/perl/wc.pl to add the "wc" command. Then, one can
do this: :perl wc Yes, this is a trivial example. There are more
useful examples, eg 'make' output parsing along the lines of emacs's
"compile" mode. The tcl extension is similar and enabled by default since
we ship with tcl.)

show more ...

Link Dutch catalog with nl_NL instead of da_DK

Add ru_RU as alias to ru_SU

Added a missing \ for installing perl modules.
2.2 and 2.1.6 candidate.

Merge from the 2.2 branch: avoid including the API stuff when building
vi for the fixit floppy. Perhaps we'll find a more elegant solution
some day, by now it has proven to work reasonably.