[M3devel] [M3commit] CVS Update: cm3

Jay K jay.krell at cornell.edu
Fri Jul 30 03:58:45 CEST 2010


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.
 
 
What isn't easy though is "stitching together of multiple sparse pieces".
overrides can do that today.
$ORIGIN and the old full paths are both at odds with that though.
If you make a complete, full paths are wrong.
If you make an incomplete copy, $ORIGIN is wrong.
 
 
"stitching together of multipl sparse pieces" is maybe the job of LD_LIBARY_PATH though, and makes no guarantees (since you might have duplicates and it becomes order-dependent).
 
 
It might help if the "new" root is symlinks..except it doesn't -- no way for old files to point to new.
 
General point noted. And if I fail, we have m3commit.
 
 
Gotta run,
 - Jay
 
> From: rcolebur at SCIRES.COM
> To: m3devel at elegosoft.com
> Date: Thu, 29 Jul 2010 21:35:30 -0400
> Subject: Re: [M3devel] [M3commit] CVS Update: cm3
> 
> Jay, before you go removing stuff on an assumption, maybe you should check with the group. I do know what this message means and it does have value.
> Regards,
> Randy
> 
> ________________________________________
> From: Jay Krell [jkrell at elego.de]
> Sent: Wednesday, July 28, 2010 12:22 PM
> To: m3commit at elegosoft.com
> Subject: [M3commit] CVS Update: cm3
> 
> CVSROOT: /usr/cvs
> Changes by: jkrell at birch. 10/07/28 16:22:03
> 
> Modified files:
> cm3/m3-sys/cm3/src/: M3Build.m3
> 
> Log message:
> remove more of the code for: remove the "ignoring override" print out, I think few people know it means and fewer (nobody) finds it useful
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20100730/9d8a79f5/attachment-0002.html>


More information about the M3devel mailing list