Hello, > >> >> Basically space requirements. We would like to provide many more >> languages as full installation sets instead of language-packs only, >> but we have only limited space on the normal mirrors. So we need to reconsider the requestet space for ./localized or/and think about a other concept for the localized binary's. > > Using MirrorBrain as the only distribution solution is not what we/I > want. From my POV it is very welcome to use it as an additional solution. >From the look at it, it seems to be a good solution finding a near mirror, it also check the mirror self for the hosted content. Sure it is still needed to have a list of the different mirrors. And also the bouncer to check for new updates.
>> Valid points. So I think it makes more sense to stick to the existing >> rule of providing official releases in the main area, including all >> localizations, and provide RCs on ../extended. In contrast to >> previous releases we would just place more full installation sets on >> ../extended instead of only language-packs, which previously was the >> case for many languages. >> >> The only potential problem I see is that we might get more QA >> approvals for the RC (and thus official releases to provide in the >> main area) than we have space for on the normal mirrors. But I think >> we can handle this by then providing these (late) languages on the >> extended mirrors only. This would be the only change to the currently >> existing guidelines, but I don't see another solution because space >> constraints would force us at some point to resort to the space on >> ../extended. >> >> Am I making sense? > > Your opinion and Florian's opinion make sense. > I will stay to provide localizations via main (regular) mirrors as > long as there's enough disk space available. If not I have to use > ../extended for the rest of the files. Hm my calculations with http://distribution.openoffice.org/mirrors/ are wrong, because this list is not that up2date. There are more mirrors hosting the extended than listed (around 11 more). But also some of the extended host are down but I did not check all till now. For this releases i don't see a other solution than todo the way as suggested. But looking forward, how much space do we have to calculate with? How many languages will it be? OS: linux32/64; win32; mac ppc/intel; solaris sparc/x86; Java: with/without 7*2=14 // systems and different java 14-1=13 // a system can only be installed with java 13*150MB=1950MB // a singel language with all different architectures ~30GB/~2GB=15 // max space on /localized atm -> we can host without change max up to 15 languages with a full installation Is there a other possibility than extending the mirror space to solve that problem? Greetings Florian --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
