[Design] Need clarification on a 0.7 Calendar tenant

[Mike Taylor]

On the wiki page for 0.7 planning (see  
http://wiki.osafoundation.org/bin/view/Projects/ZeroPointSevenPlanning  
) I read:

	Support a more robust user experience for people outside OSAF testing  
the calendar
	 - Release packaging - enable users to install and run on all three  
platforms

My take on that text was that I would need to ensure that on modern  
Linux distros (Ubuntu, FC4, Gentoo) Chandler would be installable and  
would start.

On IRC today we had a discussion about building and running on Ubuntu  
(breezy badger).  One of the issues raised was that because by default  
the gcc/gcj 3.4 toolset is not installed we would need to either  
install the 3.4.x toolset or to build Chandler using the 4.0.x toolset  
(which has known issues.)

Because of the known issues with gcc/gcj 4.0.x (see  
http://lists.osafoundation.org/pipermail/pylucene-dev/2006-February/ 
thread.html for one of them ) we cannot currently build using the 4.0.x  
toolset -- my goal was to determine the steps and document what is  
needed to get the gcc/gcj 3.4.x toolset to work on Ubuntu.

Because the discussion on IRC highlighted that I could be mis-reading  
the tenant it was suggested that I post here to get clarification from  
the team.

My recommendation is to use the gcc/gcj 3.4.x toolset, document the  
requirements for Ubuntu (which we are trying to make our "official"  
Linux platform) and then we can migrate the QA and Tinderbox computers  
and make Ubuntu our new official Linux platform.
	
---
Bear

Build and Release Engineer
Open Source Applications Foundation (OSAF)
bear at osafoundation.org
http://www.osafoundation.org

bear at code-bear.com
http://code-bear.com

PGP Fingerprint = 9996 719F 973D B11B E111  D770 9331 E822 40B3 CD29

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://lists.osafoundation.org/pipermail/design/attachments/20060217/55003ad5/PGP.pgp