From owner-freebsd-current Wed Oct 28 11:29:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA04144 for freebsd-current-outgoing; Wed, 28 Oct 1998 11:29:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA04098; Wed, 28 Oct 1998 11:29:15 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id VAA13785; Wed, 28 Oct 1998 21:28:29 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199810281928.VAA13785@gratis.grondar.za> To: sos@FreeBSD.ORG cc: current@FreeBSD.ORG, ports@FreeBSD.ORG Subject: Re: Who built XFree86 with Kerberos? In-Reply-To: Your message of " Wed, 28 Oct 1998 10:53:11 PST." <199810281853.KAA29876@hub.freebsd.org> References: <199810281853.KAA29876@hub.freebsd.org> Date: Wed, 28 Oct 1998 21:28:28 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG wrote: > In reply to Doug White who wrote: > > I have a mailing list of confused users who want to meet you. > > > > Please rebuild X without Kerberos; Kerberos is certainly *NOT* the common > > case. > > Same holds for lots of the packages :( The problem is obly on one machine; the port-builder. That one clearly has KerberosIV (eBones) enabled, and the X is Kerberos-enabled. As a consequence, all X-ports are Kerberos-enabled. Fix 1 thing, fix'em all. What machine is used to build all the ports? M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message