[M3devel] building packages from source from cvs -- odbc

[Jay K]

> My saying this year seems to be "That which is not tested is broken".  In the face of any change, including the mere passage of time (e.g. y2k):   That which is not tested often and recently is probably broken.    Running automated tests daily, or at least in a loop that might take over a day, is how you know what is working.   I believe someone recently recovered the ESC stuff. Probably Olaf.   - Jay
 > Date: Thu, 17 May 2012 21:17:34 -0400
> From: hendrik at topoi.pooq.com
> To: m3devel at elegosoft.com
> Subject: Re: [M3devel] building packages from source from cvs -- odbc
> 
> On Thu, May 17, 2012 at 11:29:16PM +0000, Jay K wrote:
> > 
> > I have not built the entire tree since that stuff came in.Oops.  
> 
> My saying this year seems to be "That which is not tested is broken".
> 
> > If the goal is to get some sort of .deb, to see what it is, to give it to someone else, do this:    cd scripts    rm PKGSDB    edit down pkginfo.txt     hm, oops, this stuff isn't in there?      The same information might be duplicated in pylib.py?   I think I fixed that..based on a quick read.       Maybe we pickup all m3makefiles? Maybe.    Just rm -rf from your tree anything that is giving you trouble now, as you've already built lots of stuff.     - Jay
> 
> That's the way to get ahead at this point, yes.
> 
> I will have to take a look at ESC sometime, though.  It looks like fun.  
> This is the stuff that processes all the mutex comments in Trestle, 
> right?
> 
> I really had thought it was long-lost code, never to be seen again.  Or 
> has someone started writing it anew?
> 
> -- hendrik
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20120518/b1685039/attachment-0002.html>