tora - Takamichi Akiyama wrote:
Hi Tora,
Until then, how about this kind of revised idea?
Stop building individual language versions of installation binary set
for each platform. (same as previous post)
Build a language-neutral installation binary for each platform. (new)
It might includes the limited amount of resources of each language
to solely accomplish installation process. (new)
Build every language-packs. Those might be just a zip file, not
necessarily a self-extract .exe file. The contents of the lang-pack
will be automatically extracted by the installer above. (new)
A user download both
- the language-neutral installation binary and
- desired language-pack(s)
also a good point. :-)
I think all of us have been looking for how to treat the redundancy
that every language-dependent full-set installation binary share the
functionally and/or physically identical files, e.g. .dll files, with
all other languages' binaries.
Oh yes!
The amount of those redundant files might occupy 90% of the capacity
of our mirror servers, I bet. If we could remove or reduce such the
redundancy, the required capacity of a mirror server would decrease by
90% and the duration to upload and distribute files would shorten by 90%.
In any case it would be a dramatic decrease and we would have 100%
happ[y|ier] mirror admins.
I just want to mention that *IMHO* this is nothing for another minor
release (3.x) but the next major. Because here we need to do hugh
re-coding in the installation process and also need to test this deeply
before thinking of a Beta release.
On 25.11.2010 21:20, Marcus Lange wrote:
Furthermore, not all languages/platforms will be tested and approved by
the community; this is especially for smaller native lang teams. So, how
to split the tested files from the untested? And how to get the approved
RC builds into a multi-lang installer as stable without to
rebuild/repackage?
I am a pragmatic software engineer. So it is slightly hard for me to
understand the necessity of approval by native lang teams, even though I
respect it.
In reality, those whose relevant native lang team does not approve some
of or all of the RC builds could find their installation binary in the
extended/ directory. And they (could be majority) do so. That is, I bet,
well-known reality. However, I do not oppose the process of approval.
For me it's also sad to see that some teams cannot release the files
what their translators have localized due to short manpower, time,
hardware...
But at least the files are available as RCs as we have splitted the
stable (download.openoffice.org/index.html) and unstable parts
(download.openoffice.org/all_rc.html) since a few releases. IMHO this is
very successful.
And it would work with 100+ languages but only if the mirrors would
still play the game with us. Now we have tried to convince the mirror
admins to help us here with the compromise to split the localized builds
into packages. I hope this will work for the near future.
But you are right with your idea. We have work on the root cause of the
problem and this is to reduce the amount of redundant files inside the
installation sets. Somehow...
Best regards
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
