On Monday 21 June 2004 10:17, Chris Baird wrote:
>
> For the comprehensionly-challenged, I'm soliciting ideas how I can
> best 'cleanly' maintain a munged base system (...without going as far
> as a LOCALBASE=/usr in mk.conf), preferably something that is robust
> across complete source rebuilds.

Make your modifications, and use some other SCM's mechanisms to maintain 
local changes (bitkeeper or perforce.)

So, rsync regularly the NetBSD CVS repository, and regularly "cvs 
update" and then merge in any changes to a local branch you would 
maintain--keeping the GNU version of gzip as the authoritative 
trunk/head version each time changes are made to that area of the tree 
in the imported source.

This is really the best way to do this, and you get the added bonus of 
having your own changes versioned alongside the master copy for 
comparison purposes.

This is exactly what these kinds of systems are for. Heck, you could 
probably do it with CVS too, but other tools make it easier.