You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Mathias Bauer <Ma...@gmx.net> on 2011/10/30 19:49:17 UTC

Moving ext_src to Apache

Moin,

thinking a bit about what would be the best to do I would like to sort
all tarballs into several categories:

(1) external source tarballs with an AL compatible license
(2) external source tarballs with weak copyleft license
(3) external source tarballs with strong copleft license

The topics we need to consider are differnt in these three sections.

Everybody should know how external modules are built now:
Currently we build all external modules as part of the "main" directory:
a script in the folder of the module unpacks the tarball from the local
ext_src folder into the build sub folder of the module, applies patches
if necessary and then builds the module from its build folder (not from
its source folder as with all "internal" modules).

(1) AL compatible license

We don't have problems to add them to our repository, but we should
think a little bit about how we do it.
As we are now thinking about moving external tarballs into svn, I don't
see a reason to keep their build directories inside of "main" - at least
not for those components that will always be built as external module
and so will never be used from the system. It looks strange to me to
have the tarballs in one part of the svn repo, copy it into another part
and then build from there.
So IMHO it would make sense to move these tarballs into the folder of
the module that builds it and then decise whether the whole module
should be moved from "main" to "external".

(2) Weak Copyleft license

It seems as if we want to keep at least HunSpell, maybe more, and
according to the Apache rules we must deliver them as binaries in our
source tree. As we don't take these binaries from the original projects
as they are (for several reasons), we must build them from the sources
ourselves and that must happen somewhere outside of the "regular" OOo
build. We already do that with the "mozilla" module if the
"--disable-build-mozilla" option in configure is used. In that case
precompiled binaries are expected to be in the "moz" module.
It don't know how this will look in the future, but it seems clear to me
that we will need the sources for these components. So I will cpüy these
source tarballs into our "external" sub repo as planned.

(3) Strong Copyleft license

In the end we don't want to keep them, so sooner or later we will remove
them from our repository. The question I have now is: shall we move them
to our repository first and remove them later (as we do with the
lgpl/mpl stuff that currently is inside the source code tree) or can be
leave out at least some of them now? Different to the weak copyleft
components, the strong copyleft ones are of no use for us, neither in
source nor in binary form.
To keep things simple for now: if nobody asks for the opposite, I will
copy them into our "external" sub repo, but that's open for discussion.

Regards,
Mathias

Re: Moving ext_src to Apache

Posted by Pedro Giffuni <pf...@apache.org>.
--- On Mon, 10/31/11, Rob Weir <ro...@apache.org> wrote:
...
> > (2) Weak Copyleft license
> >
> > It seems as if we want to keep at least HunSpell,
> maybe more, and
> > according to the Apache rules we must deliver them as
> binaries in our
> > source tree. As we don't take these binaries from the
> original projects
> > as they are (for several reasons), we must build them
> from the sources
> > ourselves and that must happen somewhere outside of
> the "regular" OOo
> > build. We already do that with the "mozilla" module if
> the
> 
> I don't believe that there is any requirement to place
> these modules outside of the Apache SVN.  The requirement
> is around *releases*, not *builds*.  We cannot include the
> source of weak copyleft components in our releases.  But we
> can host them in SVN.
> 
> In general, I don't think that there is any real advantage,
> in terms of Apache license and release policy, of moving
> code to Apache Extras.

Hmm.. we are talking about mozilla and hunspell, right?
I don't see any advantage in attempting to maintain that
stuff in-house. If someone is going to maintain that, I
won't object but at least for FreeBSD we will be using
the available binaries which are pretty well maintained,
specially concerning security issues.

Once the headers are changed, one thing that we do need
to maintain in Apache Extras is the reportbuilder module
and all it's dependencies. Those are all GPLd and there
doesn't seem to be any possible replacement.

Pedro.

Re: Moving ext_src to Apache

Posted by Rob Weir <ro...@apache.org>.
On Sun, Oct 30, 2011 at 2:49 PM, Mathias Bauer <Ma...@gmx.net> wrote:
> Moin,
>
> thinking a bit about what would be the best to do I would like to sort
> all tarballs into several categories:
>
> (1) external source tarballs with an AL compatible license
> (2) external source tarballs with weak copyleft license
> (3) external source tarballs with strong copleft license
>
> The topics we need to consider are differnt in these three sections.
>
> Everybody should know how external modules are built now:
> Currently we build all external modules as part of the "main" directory:
> a script in the folder of the module unpacks the tarball from the local
> ext_src folder into the build sub folder of the module, applies patches
> if necessary and then builds the module from its build folder (not from
> its source folder as with all "internal" modules).
>
> (1) AL compatible license
>
> We don't have problems to add them to our repository, but we should
> think a little bit about how we do it.
> As we are now thinking about moving external tarballs into svn, I don't
> see a reason to keep their build directories inside of "main" - at least
> not for those components that will always be built as external module
> and so will never be used from the system. It looks strange to me to
> have the tarballs in one part of the svn repo, copy it into another part
> and then build from there.
> So IMHO it would make sense to move these tarballs into the folder of
> the module that builds it and then decise whether the whole module
> should be moved from "main" to "external".
>
> (2) Weak Copyleft license
>
> It seems as if we want to keep at least HunSpell, maybe more, and
> according to the Apache rules we must deliver them as binaries in our
> source tree. As we don't take these binaries from the original projects
> as they are (for several reasons), we must build them from the sources
> ourselves and that must happen somewhere outside of the "regular" OOo
> build. We already do that with the "mozilla" module if the

I don't believe that there is any requirement to place these modules
outside of the Apache SVN.  The requirement is around *releases*, not
*builds*.  We cannot include the source of weak copyleft components in
our releases.  But we can host them in SVN.

In general, I don't think that there is any real advantage, in terms
of Apache license and release policy, of moving code to Apache Extras.
 It doesn't enable anything that would not already be permitted.
Where you host the code does not really change anything.  It is what
you put in the release that really counts.

However, there are advantages to having the code in SVN rather than
Apache Extras:

1) Backups and support provided by Apache Infra

2) Access controlled automatically maintained per our committer list

3) All committer changes automatically covered by iCLA

4) Ability to have a coherent project history in a single repository

5) Ability to branch across the entire project, including the external
dependencies.  This might be very important when we start integrating
code from Symphony, for example.

So I don't see any great advantage to hosting the 3rd party components
outside of our AOOo SVN, even non-Apache licensed ones.

> "--disable-build-mozilla" option in configure is used. In that case
> precompiled binaries are expected to be in the "moz" module.
> It don't know how this will look in the future, but it seems clear to me
> that we will need the sources for these components. So I will cpüy these
> source tarballs into our "external" sub repo as planned.
>
> (3) Strong Copyleft license
>
> In the end we don't want to keep them, so sooner or later we will remove
> them from our repository. The question I have now is: shall we move them
> to our repository first and remove them later (as we do with the
> lgpl/mpl stuff that currently is inside the source code tree) or can be
> leave out at least some of them now? Different to the weak copyleft
> components, the strong copyleft ones are of no use for us, neither in
> source nor in binary form.
> To keep things simple for now: if nobody asks for the opposite, I will
> copy them into our "external" sub repo, but that's open for discussion.
>

I think we just keep them in our SVN, but remove them as we work
toward our first release.  There might even be areas where we keep
LGPL header files in our tree in order to resolve dependencies that
will be resolved at runtime based on platform available modules.

-Rob

> Regards,
> Mathias
>

Re: Moving ext_src to Apache

Posted by Andre Fischer <af...@a-w-f.de>.
Hi Pedro,


On 04.12.2011 17:19, Pedro Giffuni wrote:
> Hi Andre;
>
> --- Ven 2/12/11, Andre Fischer<af...@a-w-f.de>  ha scritto:
>
>> Hi,
>>
>> I changed bootstrap.1, fetch_tarballs.sh and ooo.lst to use
>> the new
>> ext_sources directory.  For details please see issue
>> 118663
>> (https://issues.apache.org/ooo/show_bug.cgi?id=118663).
>>
>
> The BSDs (and Solaris?) don't carry /bin/bash, please try to
> keep using /bin/sh instead.

There is no bash for BSD?  Why?

>
> (No idea if there are bashisms in the script now)

Well, when it did not break your build then probably not :-)

-Andre

>
> cheers,
>
> Pedro.

Re: Moving ext_src to Apache

Posted by eric b <er...@free.fr>.
Hi Pedro,


Le 4 déc. 11 à 17:19, Pedro Giffuni a écrit :

> Hi Andre;
>
> --- Ven 2/12/11, Andre Fischer <af...@a-w-f.de> ha scritto:
>
>> Hi,
>>
>> I changed bootstrap.1, fetch_tarballs.sh and ooo.lst to use the  
>> new  ext_sources directory.  For details please see issue
>> 118663
>> (https://issues.apache.org/ooo/show_bug.cgi?id=118663).
>>
>
> The BSDs (and Solaris?) don't carry /bin/bash, please try to keep  
> using /bin/sh instead.


Shall we force all major OSs to use prehistoric shells just because  
BSDs or  dead alive Solari don't use bash ?

I'm sorry but I'd like to understand why ...


Eric

-- 
qɔᴉɹə
Projet OOo4Kids : http://wiki.ooo4kids.org/index.php/Main_Page
L'association EducOOo : http://www.educoo.org
Blog : http://eric.bachard.org/news






Re: Moving ext_src to Apache

Posted by Pedro Giffuni <pf...@apache.org>.
Hi Andre;

--- Ven 2/12/11, Andre Fischer <af...@a-w-f.de> ha scritto:

> Hi,
> 
> I changed bootstrap.1, fetch_tarballs.sh and ooo.lst to use
> the new 
> ext_sources directory.  For details please see issue
> 118663 
> (https://issues.apache.org/ooo/show_bug.cgi?id=118663).
> 

The BSDs (and Solaris?) don't carry /bin/bash, please try to
keep using /bin/sh instead.

(No idea if there are bashisms in the script now)

cheers,

Pedro.

Re: Moving ext_src to Apache

Posted by Andre Fischer <af...@a-w-f.de>.
Hi,

I changed bootstrap.1, fetch_tarballs.sh and ooo.lst to use the new 
ext_sources directory.  For details please see issue 118663 
(https://issues.apache.org/ooo/show_bug.cgi?id=118663).

For a short time a small set of external libraries is still loaded from 
hg.services.openoffice.org.  These will ago away when glibc is removed 
(I will apply my changes for this later this day) and when berkeley db 
is removed.

Regards,
Andre

On 29.11.2011 00:04, Mathias Bauer wrote:
> Am 30.10.2011 19:49, schrieb Mathias Bauer:
>
>> Moin,
>>
>> thinking a bit about what would be the best to do I would like to sort
>> all tarballs into several categories:
>>
>> (1) external source tarballs with an AL compatible license
>> (2) external source tarballs with weak copyleft license
>> (3) external source tarballs with strong copleft license
>
> I decided to make things simple. So I just checked in the source
> tarballs for (1) and (2), means sources with category A and B license.
> You will find them in the new folder
>
> trunk/ext_sources
>
> Basically we should be able to use this folder in the build once we have
> solved the remaining problems (see below). "By luck" this is the default
> location where the OOo build looks for external tarballs if no parameter
> was set in configure.
>
> So I made an attempt to build with it (Ubuntu 11.10 64 Bit) and nearly
> got through the build:
>
> (1) ./configure (no parameters!)
> (2) *no* bootstrap (I took dmake from the system and skipped the
> fetch_tarballs that way)
> (3) build
>
> I got problems only in three cases:
>
> (1) berkeley DB was missed in two places
> (2) rhino missed swingExtSrc (this was discussed on the list already,
> maybe we have a solution to fix that?)
> (3) I then provided the missing tarballs temporarily and continued with
> the build. Now I got a problem in instsetoo_native (building of deb
> files didn't work, perhaps the system epm doesn't work here, I heard
> that others were more successfull). But the archive install set was
> build and worked!
>
> That looks as if we are close to a build without external stuff with
> strong copyleft license.
>
> We still have to define how to deal with the weak copyleft stuff. I
> found the following Category B licenses: MPL, CPL, CDDL. As we still
> didn't get a definitive statement if we are allowed to keep them in svn
> if we make sure that they are not built by default and they are not part
> of our source releases, it seems that there is a common agreement to
> keep them for now and possibly remove them later. Even if we had to
> remove them, we now have an intermediate step that helps us a bit
> forward, IMHO.
>
> At this time my checkin does not change anything for the build, but you
> can try it by providing a dmake instance before and not calling
> "bootstrap" as described above.
>
> Now we can start from there and change our build so that it uses this
> folder by default.
>
> Regards,
> Mathias
>

Re: Moving ext_src to Apache

Posted by Andre Fischer <af...@a-w-f.de>.
Hi,

I changed bootstrap.1, fetch_tarballs.sh and ooo.lst to use the new 
ext_sources directory.  For details please see issue 118663 
(https://issues.apache.org/ooo/show_bug.cgi?id=118663).

For a short time a small set of external libraries is still loaded from 
hg.services.openoffice.org.  These will ago away when glibc is removed 
(I will apply my changes for this later this day) and when berkeley db 
is removed.

Regards,
Andre

On 29.11.2011 00:04, Mathias Bauer wrote:
> Am 30.10.2011 19:49, schrieb Mathias Bauer:
>
>> Moin,
>>
>> thinking a bit about what would be the best to do I would like to sort
>> all tarballs into several categories:
>>
>> (1) external source tarballs with an AL compatible license
>> (2) external source tarballs with weak copyleft license
>> (3) external source tarballs with strong copleft license
>
> I decided to make things simple. So I just checked in the source
> tarballs for (1) and (2), means sources with category A and B license.
> You will find them in the new folder
>
> trunk/ext_sources
>
> Basically we should be able to use this folder in the build once we have
> solved the remaining problems (see below). "By luck" this is the default
> location where the OOo build looks for external tarballs if no parameter
> was set in configure.
>
> So I made an attempt to build with it (Ubuntu 11.10 64 Bit) and nearly
> got through the build:
>
> (1) ./configure (no parameters!)
> (2) *no* bootstrap (I took dmake from the system and skipped the
> fetch_tarballs that way)
> (3) build
>
> I got problems only in three cases:
>
> (1) berkeley DB was missed in two places
> (2) rhino missed swingExtSrc (this was discussed on the list already,
> maybe we have a solution to fix that?)
> (3) I then provided the missing tarballs temporarily and continued with
> the build. Now I got a problem in instsetoo_native (building of deb
> files didn't work, perhaps the system epm doesn't work here, I heard
> that others were more successfull). But the archive install set was
> build and worked!
>
> That looks as if we are close to a build without external stuff with
> strong copyleft license.
>
> We still have to define how to deal with the weak copyleft stuff. I
> found the following Category B licenses: MPL, CPL, CDDL. As we still
> didn't get a definitive statement if we are allowed to keep them in svn
> if we make sure that they are not built by default and they are not part
> of our source releases, it seems that there is a common agreement to
> keep them for now and possibly remove them later. Even if we had to
> remove them, we now have an intermediate step that helps us a bit
> forward, IMHO.
>
> At this time my checkin does not change anything for the build, but you
> can try it by providing a dmake instance before and not calling
> "bootstrap" as described above.
>
> Now we can start from there and change our build so that it uses this
> folder by default.
>
> Regards,
> Mathias
>

[code] Berkeley DB has non-permissive license [was: Re: Moving ext_src to Apache]

Posted by Oliver-Rainer Wittmann <or...@googlemail.com>.
Hi,


On 30.11.2011 11:48, Jürgen Schmidt wrote:
> On 11/29/11 12:04 AM, Mathias Bauer wrote:
>> Am 30.10.2011 19:49, schrieb Mathias Bauer:
>>
>>> ...
>>
>> I got problems only in three cases:
>>
>> (1) berkeley DB was missed in two places
> seems that we have overseen berkeley db here. Ok we have to find
> alternatives.
>
> One use case is the managing of extensions (extensions.db,
> uno_packages.db, ...)
>
> And the other use case is inthe help system.
>

I am volunteering to work on this.

Berkeley DB is used in modules l10ntools, xmlhelp and desktop.
I already had a look at its usage in l10ntools - it is 'dead' code which 
never has been used. Thus, this dependency will go quite easy.

Any further help is welcome.

Best regards, Oliver.

Re: Moving ext_src to Apache

Posted by Jürgen Schmidt <jo...@googlemail.com>.
On 11/29/11 12:04 AM, Mathias Bauer wrote:
> Am 30.10.2011 19:49, schrieb Mathias Bauer:
>
>> Moin,
>>
>> thinking a bit about what would be the best to do I would like to sort
>> all tarballs into several categories:
>>
>> (1) external source tarballs with an AL compatible license
>> (2) external source tarballs with weak copyleft license
>> (3) external source tarballs with strong copleft license
>
> I decided to make things simple. So I just checked in the source
> tarballs for (1) and (2), means sources with category A and B license.
> You will find them in the new folder
>
> trunk/ext_sources
>
> Basically we should be able to use this folder in the build once we have
> solved the remaining problems (see below). "By luck" this is the default
> location where the OOo build looks for external tarballs if no parameter
> was set in configure.
>
> So I made an attempt to build with it (Ubuntu 11.10 64 Bit) and nearly
> got through the build:
>
> (1) ./configure (no parameters!)
> (2) *no* bootstrap (I took dmake from the system and skipped the
> fetch_tarballs that way)
> (3) build
>
> I got problems only in three cases:
>
> (1) berkeley DB was missed in two places
seems that we have overseen berkeley db here. Ok we have to find 
alternatives.

One use case is the managing of extensions (extensions.db, 
uno_packages.db, ...)

And the other use case is inthe help system.

> (2) rhino missed swingExtSrc (this was discussed on the list already,
> maybe we have a solution to fix that?)

This becomes obsolete with the update to a newer Rhino version and the 
available patch.

> (3) I then provided the missing tarballs temporarily and continued with
> the build. Now I got a problem in instsetoo_native (building of deb
> files didn't work, perhaps the system epm doesn't work here, I heard
> that others were more successfull). But the archive install set was
> build and worked!
not out of the box and i went back to use the patched version of epm. 
More work is necessary here to understand the packaging process. And 
it's only a build tool similar to make or dmake.

>
> That looks as if we are close to a build without external stuff with
> strong copyleft license.
>
> We still have to define how to deal with the weak copyleft stuff. I
> found the following Category B licenses: MPL, CPL, CDDL. As we still
> didn't get a definitive statement if we are allowed to keep them in svn
> if we make sure that they are not built by default and they are not part
> of our source releases, it seems that there is a common agreement to
> keep them for now and possibly remove them later. Even if we had to
> remove them, we now have an intermediate step that helps us a bit
> forward, IMHO.
i think it will definitely help us for now. And the work on finding 
alternatives is ongoing.

>
> At this time my checkin does not change anything for the build, but you
> can try it by providing a dmake instance before and not calling
> "bootstrap" as described above.
>
> Now we can start from there and change our build so that it uses this
> folder by default.
yes, that sounds good to me. I would leave the download opportunity in 
place. That would allow that at least in a source release all configure 
switches would work and won't break anything. But of course nothing 
would be used by default.

Juergen

Re: Moving ext_src to Apache

Posted by Mathias Bauer <Ma...@gmx.net>.
Am 30.10.2011 19:49, schrieb Mathias Bauer:

> Moin,
> 
> thinking a bit about what would be the best to do I would like to sort
> all tarballs into several categories:
> 
> (1) external source tarballs with an AL compatible license
> (2) external source tarballs with weak copyleft license
> (3) external source tarballs with strong copleft license

I decided to make things simple. So I just checked in the source
tarballs for (1) and (2), means sources with category A and B license.
You will find them in the new folder

trunk/ext_sources

Basically we should be able to use this folder in the build once we have
solved the remaining problems (see below). "By luck" this is the default
location where the OOo build looks for external tarballs if no parameter
was set in configure.

So I made an attempt to build with it (Ubuntu 11.10 64 Bit) and nearly
got through the build:

(1) ./configure (no parameters!)
(2) *no* bootstrap (I took dmake from the system and skipped the
fetch_tarballs that way)
(3) build

I got problems only in three cases:

(1) berkeley DB was missed in two places
(2) rhino missed swingExtSrc (this was discussed on the list already,
maybe we have a solution to fix that?)
(3) I then provided the missing tarballs temporarily and continued with
the build. Now I got a problem in instsetoo_native (building of deb
files didn't work, perhaps the system epm doesn't work here, I heard
that others were more successfull). But the archive install set was
build and worked!

That looks as if we are close to a build without external stuff with
strong copyleft license.

We still have to define how to deal with the weak copyleft stuff. I
found the following Category B licenses: MPL, CPL, CDDL. As we still
didn't get a definitive statement if we are allowed to keep them in svn
if we make sure that they are not built by default and they are not part
of our source releases, it seems that there is a common agreement to
keep them for now and possibly remove them later. Even if we had to
remove them, we now have an intermediate step that helps us a bit
forward, IMHO.

At this time my checkin does not change anything for the build, but you
can try it by providing a dmake instance before and not calling
"bootstrap" as described above.

Now we can start from there and change our build so that it uses this
folder by default.

Regards,
Mathias