Date: Sat, 27 Sep 2003 21:52:13 +0200 From: Erik Trulsson <ertr1013@student.uu.se> To: "Walter C. Pelissero" <walter@pelissero.de> Cc: questions@freebsd.org Subject: Re: auto-patching the system Message-ID: <20030927195213.GA40669@falcon.midgard.homeip.net> In-Reply-To: <16245.50389.246629.356670@hyde.home.loc> References: <16245.50389.246629.356670@hyde.home.loc>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Sep 27, 2003 at 07:11:49PM +0200, Walter C. Pelissero wrote: > I keep my src tree updated with cvsup, but I start to accumulate > patches to kernel or programs that I'd like to include automatically > each time I recompile the kernel (pretty often) or I do a "make world" > (much less often). > > Those are usually patches that have been already put forward to the > attention of the maintainers with a send-pr, but got forgotten or > simply ignored possibly because considered not interesting. > > At the moment I simply manually copy the modified files into the > source tree before recompiling, but, of course, next time I do a > cvsup, the changes are gone, requiring me to repeat the process next > time I compile (and likely forgetting some stuff). > > Is there already any pre-canned way to include those patches at > compile time? (A parallel source tree, for instance.) There are probably more than one way to keep local patches to the source, but the way I do it is: Use cvsup to get a local copy of the whole cvs repository (instead of just a checked out source tree). Then use cvs to check out the source tree from the local repository. Unlike cvsup, cvs knows how to handle local modifications. -- <Insert your favourite quote here.> Erik Trulsson ertr1013@student.uu.se
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030927195213.GA40669>