Hi Maho, *, sorry for jumping in to the issue so late,...
On 10/24/07, Maho NAKATA <[EMAIL PROTECTED]> wrote: > [...] > Still vanilla builds have some problems. > * naming problem (OpenOffice.org-2.3-en-US.dmg or something like should > be renamed) IIRC the issue just waits for a final decision. Renaming the packages themselves is easily done in the instsetoo_native/util/makefile.mk http://www.openoffice.org/issues/show_bug.cgi?id=72908 > * language pack problem. Otherwise, What problem? :-) languagepacks already work on the Mac. What is left is to define the user experience, i.e.: write/complete the specification, so that the installer can be made ready for the user. Shaun already posted the link to the working-spot for the specificaion http://wiki.services.openoffice.org/wiki/Mac_OS_X_languagepacks (What is expected in the specification is not the implementation details, but what dialogs should be displayed to the user/what the user should be asked in these dialogs - so it is simple) If you want to try it out, you can take instsetoo_native from cloph10 (after I resynced it to m235 - m233 introduced the nibs that are missing in the m228 based cws - I'll resync after I send this mail) > @good-day: > > % du -h SRC680_m233 > 51G SRC680_m233 > > Both PPC/Intel X11/AQUA. Approximately 13G for each set (13Gx4=52G). Building the full installsets leaves the staging directory behind, removing this from the disk after the dmg has been created can save lots of space. For comparison: A languagepack will be approx 15MB in size. now to PPC that was addressed in later messages: You (all) might know or not that I maintain the Mac tinderbox (the real tinderbox, not one of the buildbots) - and that this machine is a PPC machine. So buildability on PPC is always tested with that machine. And as long as it builds on PPC, of course the user should get a PPC version. I could provide installsets for selected cws on request or could build a milestone on request. But because I'm on ADSL (and thus have a slow upload) I cannot reasonably provide many languages (unless it is OK to wait hours for the upload) - Maho's setup is far more suitable for this. wrt. Distribution matters: You (all) might know or not (that is more likely :-)) - that I maintain one of the BitTorrent trackers of OOo - and that the first snapshots have been successfully distributed via BitTorrent. The distribution via BitTorrent is very useful when a few files will need to be served to many users at the very same time. It will greatly reduce the load on the distribution server in that case (in Effect more users can download (with high speed) at the same time. Instead of either a few users with high speed or many users with low speed as it is the case when a regular http/ftp server and not a P2P based system is used. ciao Christian --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
