Re: [dev] extensions, confused...
Caolan McNamara wrote: a) Identifiers In DEV300_m14 we have... a) com.sun.reportdesigner for the report designer b) so becomes org.openoffice.legacy.sun-presentation-minimizer.oxt for the presentation minimizer c) com.sun.wiki-publisher for the wiki publisher but then d) com.sun.PresenterScreen-linux_x86 for the Presenter Screen They all stay the same regardless of the platform except for com.sun.PresenterScreen-*, so what was the outcome of the last time this was discussed, should com.sun.PresenterScreen-linux_x86 just be com.sun.PresenterScreen (my preference) or should the other arch dependent extensions get mangled identifier names to encode the arch into them as well ? Appending the platform is only a means to make the identifier unique. On e could replace the platform string by anything else, as long as the result is a unique string. If there are presenter screen extensions for different platforms, then they must have different extension identifiers. Joachim b) Shared installs In DEV300_m14 the wiki publisher (alone of the extensions) cannot be installed --shared. Is this just an oversight (see http://www.openoffice.org/issues/show_bug.cgi?id=90055 for patch in that case) or deliberate ? c) Checking out OpenOffice.org What is now the canonical way to check out OpenOffice.org ? is it meant to be with alias OpenOffice3 ? i.e. we have the alias Extensions3 for "scext sdext swext tomcat apache-commons reportdesign jfreereport" we have the alias OpenOffice3 which has ... "sccomp, sdext, reportdesign, reportdesign" in it So swext and friends do not appear in the OpenOffice3 (or OpenOffice2) alias, so they don't get checked out, but they are referenced in the build.lsts. So in practice is seems to be to check out *both* OpenOffice3 and Extensions3 to get the full tree required to build C. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] extensions, confused...
Rene Engelhard wrote: Hi, Caolan McNamara wrote: a) Identifiers In DEV300_m14 we have... a) com.sun.reportdesigner for the report designer b) so becomes org.openoffice.legacy.sun-presentation-minimizer.oxt for the presentation minimizer This is changed in cws pppopt05. (It now contains the arch-identifier, too) c) com.sun.wiki-publisher for the wiki publisher but then d) com.sun.PresenterScreen-linux_x86 for the Presenter Screen a) and c) don't need the arch prefix anyway (Java, and thus arch-indep *cough*) And you missed: e) com.sun.star.PDFImport-<...> They all stay the same regardless of the platform except for com.sun.PresenterScreen-*, so what was the outcome of the last time this was discussed, should com.sun.PresenterScreen-linux_x86 just be com.sun.PresenterScreen (my preference) or should the other arch Mine too, but I think we "lost" here... It is my preference, too. The reason for appending the platform specifier was lack of time, not design. The current tools that are used for updating extensions do not yet know about the platform tag that is also available in the description.xml files. There was no time to change these tools, so we had to make the component identifiers unique with respect to platform/architecture. The tools will (hopefully) be updated in the not too distant future to take care of the platform tags. From then one we can use simple identifiers like com.sun.PresenterScreen. So, nobody "lost". Sometimes, we just have to be pragmatic. dependent extensions get mangled identifier names to encode the arch into them as well ? As said, pppopt05 has a arch-suffix for the minimizer, too (which is the left-over arch-dep extension in your list) b) Shared installs r In DEV300_m14 the wiki publisher (alone of the extensions) cannot be installed --shared. Is this just an oversight (see http://www.openoffice.org/issues/show_bug.cgi?id=90055 for patch in that case) or deliberate ?? I don't think we need to show the LGPL *AT ALL*. Neither to the user nor to the admin. OOo is LGPL and the user already uses OOo... c) Checking out OpenOffice.org What is now the canonical way to check out OpenOffice.org ? is it meant to be with alias OpenOffice3 ? i.e. we have the alias Extensions3 for "scext sdext swext tomcat apache-commons reportdesign jfreereport" we have the alias OpenOffice3 which has ... "sccomp, sdext, reportdesign, reportdesign" in it So swext and friends do not appear in the OpenOffice3 (or OpenOffice2) alias, so they don't get checked out, but they are referenced in the build.lsts. So in practice is seems to be to check out *both* OpenOffice3 and Extensions3 to get the full tree required to build Yes, that should be fixed... Not that I think the Extensions thong makes at all, given that you need the OOo tree to build those extensions anyway... Regards, Rene >[...] Best regards, Andre - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] extensions, confused...
Rene Engelhard wrote: Martin Hollmichel wrote: Once these issue are solved, we going to switch from OpenOffice2 to OpenOffice3 alias plus an additional alias for the extensions (Extensions3) And a OOo_x.y.z_src_extensions.tar.bz2 would then also make sense.. yes, agreed, Regards, Rene Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] extensions, confused...
Martin Hollmichel wrote: > Once these issue are solved, we going to switch from OpenOffice2 to > OpenOffice3 alias plus an additional alias for the extensions > (Extensions3) And a OOo_x.y.z_src_extensions.tar.bz2 would then also make sense.. Regards, Rene - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] extensions, confused...
Martin Hollmichel wrote: > Extensions can be used to achieve some modularization of the > OpenOffice.org code base and should be used to reduce the build time and > dependencies of the core OpenOffice.org builds. --enable/--disable-foo exist. > For that reason we introduced different aliases to support the > differentiation of the core and extensions. > > To my knowleadge there are at least three open issues: > > 1. move the pdf import extension into an extension only module (90061) > 2. move the report designer extension into an extension only module (90062) > 3. do we need the extensions make a prerequisite of the postprocess module ? 4. make the modules build out-of-tree with the SDK. (I don't think that they do right now) Means: They all also need their separate configures and the extension stuff then removed from the main one.. Otherwise it's mott, as you need the whole OOo tree to build them anyway, so why not ship them in there? (And use --disable/--enable-foo for deciding whether you want it or not) > > Once these issue are solved, we going to switch from OpenOffice2 to > OpenOffice3 alias plus an additional alias for the extensions Note that whoever added hyphen to the aliases missed to add it to OpenOffice3 (so I am told..) (The patch I sent which did that was closed as duplicate...) Regards, Rene - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] extensions, confused...
On Wed, 2008-05-28 at 11:27 +0200, Martin Hollmichel wrote: > Hi, > > Extensions can be used to achieve some modularization of the > OpenOffice.org code base and should be used to reduce the build time and > dependencies of the core OpenOffice.org builds. But they cannot actually be built outside an OOo setsolared build environment right ? C. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] extensions, confused...
Hi, Caolan McNamara wrote: > a) Identifiers > > In DEV300_m14 we have... > > a) com.sun.reportdesigner for the report designer > b) so becomes > org.openoffice.legacy.sun-presentation-minimizer.oxt for the > presentation minimizer This is changed in cws pppopt05. (It now contains the arch-identifier, too) > c) com.sun.wiki-publisher for the wiki publisher but then > d) com.sun.PresenterScreen-linux_x86 for the Presenter Screen a) and c) don't need the arch prefix anyway (Java, and thus arch-indep *cough*) And you missed: e) com.sun.star.PDFImport-<...> > They all stay the same regardless of the platform except > for com.sun.PresenterScreen-*, so what was the outcome of the last time > this was discussed, should com.sun.PresenterScreen-linux_x86 just be > com.sun.PresenterScreen (my preference) or should the other arch Mine too, but I think we "lost" here... > dependent extensions get mangled identifier names to encode the arch > into them as well ? As said, pppopt05 has a arch-suffix for the minimizer, too (which is the left-over arch-dep extension in your list) > b) Shared installs > r > In DEV300_m14 the wiki publisher (alone of the extensions) cannot be > installed --shared. Is this just an oversight (see > http://www.openoffice.org/issues/show_bug.cgi?id=90055 for patch in that > case) or deliberate ?? I don't think we need to show the LGPL *AT ALL*. Neither to the user nor to the admin. OOo is LGPL and the user already uses OOo... > c) Checking out OpenOffice.org > > What is now the canonical way to check out OpenOffice.org ? is it meant > to be with alias OpenOffice3 ? > > i.e. > we have the alias Extensions3 for > "scext sdext swext tomcat apache-commons reportdesign jfreereport" > we have the alias OpenOffice3 which has ... > "sccomp, sdext, reportdesign, reportdesign" in it > > > So swext and friends do not appear in the OpenOffice3 (or OpenOffice2) > alias, so they don't get checked out, but they are referenced in the > build.lsts. So in practice is seems to be to check out *both* > OpenOffice3 and Extensions3 to get the full tree required to build Yes, that should be fixed... Not that I think the Extensions thong makes at all, given that you need the OOo tree to build those extensions anyway... Regards, Rene - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] extensions, confused...
Hi, Extensions can be used to achieve some modularization of the OpenOffice.org code base and should be used to reduce the build time and dependencies of the core OpenOffice.org builds. For that reason we introduced different aliases to support the differentiation of the core and extensions. To my knowleadge there are at least three open issues: 1. move the pdf import extension into an extension only module (90061) 2. move the report designer extension into an extension only module (90062) 3. do we need the extensions make a prerequisite of the postprocess module ? Once these issue are solved, we going to switch from OpenOffice2 to OpenOffice3 alias plus an additional alias for the extensions (Extensions3) Martin c) Checking out OpenOffice.org What is now the canonical way to check out OpenOffice.org ? is it meant to be with alias OpenOffice3 ? i.e. we have the alias Extensions3 for "scext sdext swext tomcat apache-commons reportdesign jfreereport" we have the alias OpenOffice3 which has ... "sccomp, sdext, reportdesign, reportdesign" in it So swext and friends do not appear in the OpenOffice3 (or OpenOffice2) alias, so they don't get checked out, but they are referenced in the build.lsts. So in practice is seems to be to check out *both* OpenOffice3 and Extensions3 to get the full tree required to build C. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
