On 19 Mar 2007, at 14:00, André Wyrwa wrote:
Hei Maarten,
thanks for your educating mail. This is actually the first time i
get an
answer to why things are as they are, that i can understand. However,
being as ridiculously optimistic as i am ;-), i don't give up that
easily... ;-)
1. Make bouncer universal and just maintain the offerings in the
JavaScript. This is the non-ideal solution, but it would mean
that the
JavaScript only offers options that are indeed available.
What do you mean with making the bouncer 'universal'?
I take it that bouncer is php? By 'universal' i meant covering all
versions, languages and OSes that have available versions lurking
around
somewhere (of course, for that the NLPs would need to be instructed to
put their stuff in standard places). So that no version of OOo exists,
that isn't accessible from bouncer. This also includes that no link
from
a correctly tailored JavaScript to bouncer would end up dead. With
that
set up, you would have to manually tailor the JavaScript to represent
the current release availability situation. I'm assuming here that
bouncer could be made mostly automatic, so that it doesn't need to be
maintained. Then the only maintenance issue would be the JavaScript
which doesn't sound to bad to me, but also not very good. So lets look
at the other options.
Currently all builds that are on the mirror network should be in the
bouncer. If you find a build that is on the mirror network, but not
in the bouncer, please let us know so that we can get the downloads
added to the bouncer. As far as I'm aware only QA'ed builds and the
source code tarballs are placed on to the mirror network.
[...]
Shaun
--
___________________________________________________________
Yahoo! Messenger - with free PC-PC calling and photo sharing.
http://uk.messenger.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
