From owner-freebsd-arch@FreeBSD.ORG Wed Jun 4 13:48:36 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B74A37B435 for ; Wed, 4 Jun 2003 13:48:36 -0700 (PDT) Received: from storm.FreeBSD.org.uk (storm.FreeBSD.org.uk [194.242.157.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0A0943F3F for ; Wed, 4 Jun 2003 13:48:34 -0700 (PDT) (envelope-from mark@grondar.org) Received: from storm.FreeBSD.org.uk (Ugrondar@localhost [127.0.0.1]) by storm.FreeBSD.org.uk (8.12.9/8.12.9) with ESMTP id h54KmXuD044327 for ; Wed, 4 Jun 2003 21:48:33 +0100 (BST) (envelope-from mark@grondar.org) Received: (from Ugrondar@localhost)h54KmW0P044326 for arch@freebsd.org; Wed, 4 Jun 2003 21:48:33 +0100 (BST) X-Authentication-Warning: storm.FreeBSD.org.uk: Ugrondar set sender to mark@grondar.org using -f Received: from grondar.org (localhost [127.0.0.1]) by grimreaper.grondar.org (8.12.9/8.12.9) with ESMTP id h54KgoHh007445 for ; Wed, 4 Jun 2003 21:42:50 +0100 (BST) (envelope-from mark@grondar.org) From: Mark Murray Message-Id: <200306042042.h54KgoHh007445@grimreaper.grondar.org> To: arch@freebsd.org Date: Wed, 04 Jun 2003 21:42:50 +0100 Sender: mark@grondar.org X-Spam-Status: No, hits=2.2 required=5.0 tests=FROM_NO_LOWER version=2.55 X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) Subject: A proposed drastic cleanup of the telnet build. X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jun 2003 20:48:36 -0000 Hello all The (lib)telnet(d) build in our tree has always been a bit of an anachronism. We have 2 sets of code to build it, and three different flavours of telnet. We have 1) No crypto telnet, 2) crypto telnet 3) crypto telnet with Kerberos5. During a "make world", these various builds take it in turn to be built, and jump all over each other in annoying ways. This has happened for years. The 2 sets of code are for a) no crypto and b) crypto (+ KRB5). The former is an unifdef(1)ed subset of the latter. We've had continual problems with divergent code (when folks don't commit correctly to both). I propose to 'cvs rm' the 'base' telnet, and build base telnet by not defining the appropriate macros. This achieves the same result as unifdef(1). This involves .PATH: magic to the "full" telnet. For telnet-with-crypto, and telnet-with-crypto+krb5, the appropriate options are already in the tree, so the 'base' telnet will just add them if needed. This is similar in concept to the way crypto is added to bin/ed and gnu/usr.bin/cvs. secure/ and kerberos5/ will then no longer need private copies of (lib)telnet(d), and 'make world' will simplify. Functionality loss will be NIL, complexity will be reduced and a tiny bit of code bloat will be gone. The downside is that base telnet will depend on src/crypto/telnet, so folks in dodgy countries which don't allow them to have crypto source will not be able to do telnet development, and they will not get a "fresh" telnet[d] after a make world. Comments? I'm keen to go on this. M -- Mark Murray iumop ap!sdn w,I idlaH