[M3devel] more Debian packages?

[Jay K]

Yes and yes.LINUXLIBC6 and AMD64_LINUX can coexist -- different targets can coexist.But "squeeze" vs. "wheezy" will both just be LINUXLIBC6.  Please try to use I386_LINUX.I really want to stop this LINUXLIBC6 stuff...   You can share the source. But we also have outputs in the source tree (unfortunately!).    You see -- Modula-3 build system ahead of its time at the time in putting each package's output separate from the source, but that is now not uncommon, and Modula-3 then falls down because at least by default, a multi-package source tree contains its outputs... Modula-3 does things better than most folks at the time, and now worse than everyone knows is ideal and that some folks do...   Do this to switch:  ./do-cm3-all.py realclean   - Jay
 > Date: Fri, 18 May 2012 16:56:49 -0400
> From: hendrik at topoi.pooq.com
> To: m3devel at elegosoft.com
> Subject: [M3devel] more Debian packages?
> 
> Having succeeded at producing a binary .deb packages for Debian squeeze 
> (though I still have to try it out), I'm now looking at my other 
> machines.  I have a 32-bit Intel machine with wheeze (testing), and one 
> that can run squeeze (stable).  All of them have access to the same 
> NFS-mounted source tree.  Is it practical to use the same tree for two 
> different platforms (such as AMD64_LINUX and LINUXLIB6?) and will they 
> be kept separate?  Or do I need to clean it out or copy it?
> 
> (by the way, I expect making packages for different Debian releases on 
> the same hardware architecture will require a new source tree, or a 
> cleaned-out one.  In my case they'll both be LINUXLIBC6)
> 
> -- hendrik
> 
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20120518/93b0a19f/attachment-0002.html>