Hi Michael, So I should create option like --enable-oxygenoffice, and add my stuffs here? All things depending in the code directly? How should I make the download conditional? I really don't want to enforce anybody to download our extra stuffs, extensions, etc without using --enable-extra-gallery, --enable-extra-template, --enable-extra-sample, --enable-extra-font and all --with-ext-* (extension) switches. Best regards, KAMI <div class="gmail_quote">2011/4/19 Michael Meeks <<a href="mailto:michael.meeks@novell.com">michael.meeks@novell.com</a>> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi Kami, <div class="im"> On Mon, 2011-04-18 at 10:33 +0200, KAMI911 KAMI911 wrote: > I recently build a new version from libreoffice-3-4. I found that it > does not not support: > > * patches/dev300 infrastructure to patch the source </div> Right :-) <div class="im"> > * download infrastructure for additional stuffs </div> Oh ? surely we have that with ooo.lst ? <div class="im"> > Are we planning this features for bootstrap repo? Or this only for > build repo? </div> I think the idea is to try to get all of these patches turned into build conditionals - so we have a single build that auto-adapts to the underlying system, and has features that can be enabled as required. Of course, the flip side of that is - we need things flattening and conditionalizing, and fixing in the bootstrap (and other) repos - rather than continuing to pile them up inside 'build'. I guess for 3.4 'build' may still be workable, but I'd like to completely kill it on master (personally). Does that make sense ? ATB, Michael. -- <a href="mailto:michael.meeks@novell.com">michael.meeks@novell.com</a> <><, Pseudo Engineer, itinerant idiot </blockquote></div>