--- On Sat, 7/23/11, Malte Timmermann wrote: > Having extensions separated from the > source tree of the core product > doesn't mean they can't be part of some installation set. > > This is just about packaging then. >
Having the extensions in the same tarball usually makes packaging easier, and as long as "configure" makes it easy to enable/disabling them there shouldn't be any problem. I don't see good reasons for separating extensions unless there are license issues or someone wants to make extensive development, and in this last case Apache can have sub-projects (like PyLucene). I guess there might be special cases, but we will have to wait until we have a first build to look at that. cheers, Pedro. > Malte. > > On 22.07.2011 17:11, Pedro F. Giffuni wrote: > > > > --- On Fri, 7/22/11, Malte Timmermann<[email protected]> > wrote: > > > > > >> Wrt PDF Import Extension, and similar extensions: > Optional > >> extensions should not be part of a regular OOo > build or > >> source tree, > >> IMHO. > >> > > > > In general, I agree, however a pdf import extension > (with OCR) > > would be popular enough that we should include it by > default. > > This is in concordance with our ability to produce > pdf's which > > has been one or the real advantages of OOo wrt to the > leading > > commercial competitor. > > > > It has to work very well first though. > > > > cheers, > > > > Pedro. > > > > i.
