[M3devel] [M3commit] CVS Update: cm3

[hendrik at topoi.pooq.com]

On Fri, Jul 30, 2010 at 01:58:45AM +0000, Jay K wrote:
> 
> Randy, Without reading the code, what does it mean?
>  
> My first guess was I believe wrong and based on reading the code I think it is even more pointless than I previously thought.
>  
> It gets printed *all the time*, when using overrides. Look at any of the Hudson logs.
>  
> It wouldn't be printed so much in the older way of doing things, where overrides were applied haphazardly and incompletely. Now that they are used fairly consistently/correctly, it always triggers. I hope to eventually replace the overrides mechanism -- if we just put files into a designated root directory, with the same structure as "the install", then "override" is just setting that directory, optionally prepopulating with an entire copy of the current install -- depending on if you want to build up from scratch or selectively override. You could use hardlinks to speed it up, as long as our copy is delete + copy and not just copy (sometimes a copy will share with the original link(s), sometimes it will unshare, depending on the open flags (I think) or if you first delete). And "install" becomes just moving the install root, if the new one is complete.

I remember using an override somewhere ... but I don't remember where or 
why now.  But I'd worry if this change broke something.

-- hendrik