From owner-freebsd-stable@FreeBSD.ORG Thu Sep 6 15:06:57 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7DD3C16A468 for ; Thu, 6 Sep 2007 15:06:57 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from smtp808.mail.ird.yahoo.com (smtp808.mail.ird.yahoo.com [217.146.188.68]) by mx1.freebsd.org (Postfix) with SMTP id E9A1E13C45E for ; Thu, 6 Sep 2007 15:06:56 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: (qmail 1756 invoked from network); 6 Sep 2007 15:06:55 -0000 Received: from unknown (HELO ?192.168.1.2?) (thomasjudge@btinternet.com@217.44.142.35 with plain) by smtp808.mail.ird.yahoo.com with SMTP; 6 Sep 2007 15:06:55 -0000 X-YMail-OSG: akAUTiEVM1kYvaKOOatep2_XbWjx21ARMbqUTzt2fjt.bB9SIBtDkLKEh4tJATAoWxFzVEiFdqLzAYhMtGgMDow9yFnNxbcNFIiVADDFOelRVBnY8nXx Message-ID: <46E02601.7000301@tomjudge.com> Date: Thu, 06 Sep 2007 17:08:33 +0100 From: Tom Judge User-Agent: Thunderbird 1.5.0.12 (X11/20070604) MIME-Version: 1.0 To: Mark Andrews References: <200709061502.l86F2qgV070756@drugs.dv.isc.org> In-Reply-To: <200709061502.l86F2qgV070756@drugs.dv.isc.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Volker , Greg Rivers , freebsd-stable@freebsd.org Subject: Re: wpa_supplicant features and compile options X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Sep 2007 15:06:57 -0000 Mark Andrews wrote: >> On 12/23/-58 20:59, Greg Rivers wrote: >>>
I connect to certain wireless networks that >>> require the EAP_GTC and EAP_OTP features in wpa_supplicant. These >>> features are not compiled into wpa_supplicant by default. >>> >>> Using the patch below works great, but it's inconvenient having to >>> remember to apply it after every cvsup. Is there a better way to >>> accomplish this? If not, might a change such as this be committed to >>> enable GTC and OTP by default? >>> >> Greg, >> >> I'm unable to comment on including your patch into cvs, but for own >> patches like your's, I'm using a script which does 1) csup and 2) >> integrate a bunch of patches into /usr/src. >> >> HTH >> >> Volker >> >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > Or you can transfer the cvs repository and update your > source tree from that using cvs. You just leave the local > changes uncommitted. > > Alteratively you can "cvs import" the FreeBSD src periodically. > You can then commit local changes. This can also make it > easy to roll back to your previous build state. This should > take less disk space than the previous solution. > > Mark There is a better way, you can use cvsup to mirror the FreeBSD cvs repository and then use cvs to commit your changes to your own branch. There is a flag for cvs that you can set that causes branches you make to have really high branch numbers so that they are not likely to clash with the branches in the master repository. Tom