On 4/7/13 9:58 PM, Alexandro Colorado wrote: > On Sun, Apr 7, 2013 at 2:48 PM, janI <j...@apache.org> wrote: > >> On 7 April 2013 21:24, Alexandro Colorado <j...@oooes.org> wrote: >> >>> On Sun, Apr 7, 2013 at 2:12 PM, janI <j...@apache.org> wrote: >>> >>>> On 7 April 2013 20:58, Alexandro Colorado <j...@oooes.org> wrote: >>>> >>>>> I wonder if the nightly builds support customized builds, if for >>> example >>>> if >>>>> a user wants a build that has some special configuration like, >>> anti-alias >>>>> by default or a customized default templates or menu layout. >>>>> >>>>> Can the nightly build infrastructure be used to generate that? >>>>> >>>> No, our buildbot's run with a preconfigured setup, including number of >>>> tasks and configure for each task (job). >>>> >>>> >>>>> >>>>> If not, why not, what would be needed to do that. >>>>> >>>> We would need to change away from build bot, it cannot support dynamic. >>> All >>>> changes in the setup has to be done via the infrastructure svn, where >>> only >>>> a few have access. >>>> >>>> But I dont really get, if a user wants a customized build, would it not >>> be >>>> simpler for him to build it himself ? the nightly build are in my >> opinion >>>> >>> >>> Well because a user might want to just click on a build made by an >>> automated bot. >>> >>> This is done a lot by OpenSuSE studio people which can let you remaster >>> SuSE through a web interface and download the .iso, virtual machine or >>> amazon image. >>> >> I can understand the need for an OS, but do we really want to "distribute" >> different packages. The binary we deliver, have quite a lot of options for >> configuration. >> >> I admit, that I think a lot more in reducing the compile switches (a la, >> this is our binary, all compile options are solely for our >> developers/testers)....if a compile switch is usefull to a user, it should >> be an option in the program instead. >> > > The question came from a user that wonder how difficult would it be to > remaster a binary of AOO 'in the cloud' which made me think of the nightly > builds. But I understand this is more challenging that at first glance. i > guess if this was trivial, l10n would have used long ago instead of waiting > for a localized version. > >
Well the idea in general is not a bad one. But I would think more in the direction of customized packaging. Means if some body needs only a writer and dependencies in French, he can click on some options and can later on download a new packaged french writer version. Together with a good update mechanism and a stable and secure infra structure supporting such a service it can be interesting. But we are far away from this in many areas and we have far more important things that can benefit from some activity. Juergen > >> >> rgds >> jan I. >> >>> >>> >>>> to secure that our product builds and that the branches compile on >>>> different platforms. The purpose of the nightly build is not to save >> the >>>> user from installing a compiler. >>>> >>>> rgds >>>> jan I. >>>> >>>>> >>>>> Regards. >>>>> >>>>> >>>>> -- >>>>> Alexandro Colorado >>>>> Apache OpenOffice Contributor >>>>> http://es.openoffice.org >>>>> >>>> >>> >>> >>> >>> -- >>> Alexandro Colorado >>> Apache OpenOffice Contributor >>> http://es.openoffice.org >>> >> > > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
