Re: [website-dev] JRE issue/questions...
Marcus Lange <[email protected]> Tue, 08 Jun 2010 21:55:06 +0200
| Newsgroups | gmane.comp.openoffice.devel.website |
|---|---|
| Organization | Sun Microsystems GmbH |
| Message-ID | <[email protected]> |
Kay Schenk wrote: > On 06/08/2010 11:35 AM, Marcus Lange wrote: >> Kay Schenk wrote: Hello Kay, >>> oh boy! Well thanks for the update. Considering we want the user to >>> have the best experience possible, I do understand better about this. >>> It's just all these permutations and the latest change in the "schema" >>> naming has really COMPLICATED the download scripting to the point that >> with the new filename schema especially the scripting and filtering >> should be easier than before. Now it's a clear thing with the "_" and >> "-" as separator and binding characters. Before it was, hm, a mess with >> all the exceptions. >> >>> I think these are really non-maintainable almost. I do really wish >>> some of this could be re-considered, re-discussed or I don't know >>> what. >> I don't think that it's not maintainable. I can still do this stuff. ;-) > > ahemmm...well, it gives me a bit of headache to look at, and so much > repition now for the various DL servers--bouncer vs mirrorbrain...but please forget Bouncer. It wasn't maintained with current builds since many months, maybe already a year. Lets just concentrate on Mirrorbrain. :-) > maybe the website "group" isn't even the right place to address these > sorts of things (???) Ah for a nice DB backend to deal with some of this! Right, this has to be discussed on the level of project leads for releases, distribution and L10N. >> But the release process doesn't fit anymore IMHO. Every language team >> can release what and when they will. *This* is not maintainable and >> foreseeable. We should really think about to improve some steps here. > > well some sort of an organizational chit-chat is in order IMNSHO...maybe > this could be taken up by some appropriate parties at the next OO.o > conf. I'll knock on a few virtual doors to see what can be done. Yeah, good point. > I'll dig deeper this week and see if I can determine if more simplicity > is possible. Great Best regards Marcus >>> On Tue, Jun 8, 2010 at 9:17 AM, Marcus Lange <[email protected]> >>> wrote: >>>> Kay Schenk wrote: >>>>> On Fri, May 28, 2010 at 1:49 PM, Marcus Lange <[email protected]> >>>>> wrote: >>>>>> Kay Schenk wrote: >>>>>>> On 05/28/2010 01:12 PM, Marcus Lange wrote: >>>>>>>> Kay Schenk wrote: >>>> Hello Kay, >>>> >>>>>>>>> I can probably get the new idea to work...but...I'm still not >>>>>>>>> convinced >>>>>>>>> this is really the best approach. And, I think it would far >>>>>>>>> better to >>>>>>>>> spell out what the consequences will be is you don't have a JRE. >>>>>>>>> >>>>>>>> This was already tried in the past. Maybe you could take this to >>>>>>>> release >>>>>>>> meeting? >>>>>>>> >>>>>>> And? and, I don't know how to "take this to release meeting". >>>>>>> Help! and >>>>>>> thanks for your reply. >>>>>>> >>>>>> OK, I can try it and will let you know. But first I'll proof my >>>>>> assumtions >>>>>> about the functionality that needs Java. >>>>>> >>>>> great! thanks... >>>> there are several places were the JRE is used: >>>> >>>> At the moment it's not possible to take every corner into accout as I >>>> would have to ask nearly every developer. But the following are IMHO >>>> really main topics: >>>> >>>> Installer: >>>> The installer on Unix OSs are using the JRE. For Windows the native >>>> MSI technology is used. Especially on Linux we cannot know what is >>>> maybe preinstalled and how suitable it is. Of course OOo should >>>> install/run on famous and not so common distributions preferably >>>> without problems. >>>> >>>> Wizards: >>>> Every wizard that canbe used via menu "File - Wizard" is using Java. >>>> >>>> Base: >>>> The included default database engine HSQLDB needs an JRE to work. >>>> Also the Sun extensions like the Report Builder is using Java. >>>> >>>> Furthermore the story behind the integration is that we want to make >>>> sure that the user is able to work with every function in OOo (and >>>> eventually extension) out-of-the-box. A separate and manual >>>> installation of the JRE is not wished. So, this can be fullfilled at >>>> best when providing the JRE together with the OOo package. >>>> >>>> So, as a result I don't think that we can switch to builds without >>>> JRE totally. >>>> >>>> Best regards >>>> >>>> Marcus