You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Andre Fischer <af...@a-w-f.de> on 2011/12/09 10:46:42 UTC
Configure and category B
Hi all,
We are making good progress with removing category X licensed code (see
[1]). On [2], first table, you can see, that most issues have been
resolved, the remaining ones are being worked on.
Therefore I will turn my attention to handling the category B (see [3])
code. It is now part of the SVN repository and can be found as archives
in the top-level ext_sources/ directory.
As far as I understand it, the category B code will not be part of a
source release. It has to be checked out from SVN. The configure (.in)
script has to be cleaned up so that category B code is not built by
default but can be activated with a single switch, similar to the
current --enable-copyleft switch.
Does anybody have an idea for a name for the new switch better than
--enable-category-b ?
Best regards,
Andre
[1] http://www.apache.org/legal/3party.html#category-x
[2] https://cwiki.apache.org/confluence/display/OOOUSERS/IP_Clearance
[3] http://www.apache.org/legal/3party.html#category-b
Re: Configure and category B
Posted by Andre Fischer <af...@a-w-f.de>.
Hi all,
another update. It is done.
It works basically as described in my previous mail.
By default no category b code will be compiled. You can use the
--disable-category-b switch to make this more obvious but that is, of
course, not necessary.
To activate the modules in question (moz, nss, hunspell, hyphen, saxon,
rhino, beanshell, and graphite) use the --enable-category-b switch.
In order to get mozilla and nss to compile other switches are necessary
to supply more information. More on this in the "[build] Windows build
inclusive nss and moz" thread on this list.
Alternatively use --disable-mozilla to, well, disable, mozilla.
Important: the --disable-copyleft switch is gone. Therefore the nightly
build will break. Can somebody adapt the script for the build bot? Or
can I do that myself?
Regards,
Andre
Re: Configure and category B
Posted by Andre Fischer <af...@a-w-f.de>.
On 15.12.2011 16:37, Pedro Giffuni wrote:
> Hi;
>
> --- Gio 15/12/11, Rob Weir<ro...@apache.org> ha scritto:
> ...
>>
>> This is a good start, and thanks, Pedro, for reaching out
>> to them.
>> But we'll need more than a private email to make this
>> suitable for inclusion in default source releases.
>>
>
> I am aware of this.
>
> I just brought the matter here because we should be
> planning to update the bsh tarball and it's corresponding
> patch to the latest version so that we don't have
> unexpected surprises later on.
Is I said earlier, as soon as the code is officially under Apache
license, I will do the necessary changes, which will not be much work.
>
> While here:
>
> The patch for beanshell and others, carries a Makefile
> with an LGPL header: these should all be updated.
>
> In ucpp we are using already an AL2 header: perhaps
> I am naive but we should probably not use any license
> headers for files in patches and assume they are under
> the same license as the upstream code.
Hm, both patches do the same thing: create a new file (makefile.mk), not
modify a previously existing file. For a newly created patch it
naturally has a AL2 license. For an older patch I would expect that to
be part of the SGA which would allow us to change its license.
-Andre
>
> cheers,
>
> Pedro.
Re: Configure and category B
Posted by Pedro Giffuni <pf...@apache.org>.
Hi;
--- Gio 15/12/11, Rob Weir <ro...@apache.org> ha scritto:
...
>
> This is a good start, and thanks, Pedro, for reaching out
> to them.
> But we'll need more than a private email to make this
> suitable for inclusion in default source releases.
>
I am aware of this.
I just brought the matter here because we should be
planning to update the bsh tarball and it's corresponding
patch to the latest version so that we don't have
unexpected surprises later on.
While here:
The patch for beanshell and others, carries a Makefile
with an LGPL header: these should all be updated.
In ucpp we are using already an AL2 header: perhaps
I am naive but we should probably not use any license
headers for files in patches and assume they are under
the same license as the upstream code.
cheers,
Pedro.
Re: Configure and category B
Posted by Rob Weir <ro...@apache.org>.
On Wed, Dec 14, 2011 at 1:11 PM, Pedro Giffuni <pf...@apache.org> wrote:
> Hi Andre;
>
> Concerning beanshell, I asked the copyright owner last
> week and I got this answer:
>
> "Sorry we have taken so long. I hope to get to this the
> weekend after next. In the meantime please consider the
> codebase to be available under the Apache license."
>
> Don't know how this affects your plans ;).
>
This is a good start, and thanks, Pedro, for reaching out to them.
But we'll need more than a private email to make this suitable for
inclusion in default source releases.
For example:
A) A new public release of beanshell where they indicate it is
available under the Apache license. (I think that would be our
preference)
or
B) An SGA granting the code to Apache under ALv2 (not ideal, since we
don't want to fork or separately maintain beanshell)
Until then, I think we need to continue treating beanshell as category-b.
-Rob
> cheers,
>
> Pedro.
>
> --- Mer 14/12/11, Andre Fischer <af...@a-w-f.de> ha scritto:
>
>> Hi all,
>>
>> here is an update.
>>
>> The following libraries have category B license, the
>> modules in which they are used in parentheses:
>>
>> seamonkey (moz)
>> nss (nss)
>> hunspell (hunspell)
>> hyphen (hyphen)
>> saxon (saxon)
>> rhino (rhino)
>> beanshell (beanshell)
>> silgraphite (graphite)
>>
>>
>> I have added (locally, not yet checked in) a flag (working
>> title still is --{enable|disable}-category-b).
>>
>> When specified as --disable-category-b then all libraries
>> are disabled. Switches for individual libraries
>> override this.
>>
>> When specified as --enable-category-b then all libraries
>> except seamonkey and nss are enabled. Again, switches
>> for individual libraries override this.
>>
>> Seamonkey and nss are not enabled by this switch because of
>> the large and complex set of switches available for these
>> libraries. There is no simple on/off switch.
>> More information is needed by configure to prepare building
>> them.
>>
>> I am planning on testing this a bit more (especially to
>> make builds on Linux and Mac; I am working mainly on
>> Windows), decide on a name (suggestions still welcome), and
>> check in my changes on Thursday or Friday (depending on how
>> well testing goes).
>>
>> Best regards,
>> Andre
>>
Re: Configure and category B
Posted by Andre Fischer <af...@a-w-f.de>.
Hi Pedro,
On 14.12.2011 19:11, Pedro Giffuni wrote:
> Hi Andre;
>
> Concerning beanshell, I asked the copyright owner last
> week and I got this answer:
>
> "Sorry we have taken so long. I hope to get to this the
> weekend after next. In the meantime please consider the
> codebase to be available under the Apache license."
Good news.
>
> Don't know how this affects your plans ;).
No. When the transition to Apache license is done, I have to (and will)
change one or two lines in configure.in. Five minutes work.
Just give me a reminder when its done.
-Andre
>
> cheers,
>
> Pedro.
>
> --- Mer 14/12/11, Andre Fischer<af...@a-w-f.de> ha scritto:
>
>> Hi all,
>>
>> here is an update.
>>
>> The following libraries have category B license, the
>> modules in which they are used in parentheses:
>>
>> seamonkey (moz)
>> nss (nss)
>> hunspell (hunspell)
>> hyphen (hyphen)
>> saxon (saxon)
>> rhino (rhino)
>> beanshell (beanshell)
>> silgraphite (graphite)
>>
>>
>> I have added (locally, not yet checked in) a flag (working
>> title still is --{enable|disable}-category-b).
>>
>> When specified as --disable-category-b then all libraries
>> are disabled. Switches for individual libraries
>> override this.
>>
>> When specified as --enable-category-b then all libraries
>> except seamonkey and nss are enabled. Again, switches
>> for individual libraries override this.
>>
>> Seamonkey and nss are not enabled by this switch because of
>> the large and complex set of switches available for these
>> libraries. There is no simple on/off switch.
>> More information is needed by configure to prepare building
>> them.
>>
>> I am planning on testing this a bit more (especially to
>> make builds on Linux and Mac; I am working mainly on
>> Windows), decide on a name (suggestions still welcome), and
>> check in my changes on Thursday or Friday (depending on how
>> well testing goes).
>>
>> Best regards,
>> Andre
>>
Re: Configure and category B
Posted by Pedro Giffuni <pf...@apache.org>.
Hi Andre;
Concerning beanshell, I asked the copyright owner last
week and I got this answer:
"Sorry we have taken so long. I hope to get to this the
weekend after next. In the meantime please consider the
codebase to be available under the Apache license."
Don't know how this affects your plans ;).
cheers,
Pedro.
--- Mer 14/12/11, Andre Fischer <af...@a-w-f.de> ha scritto:
> Hi all,
>
> here is an update.
>
> The following libraries have category B license, the
> modules in which they are used in parentheses:
>
> seamonkey (moz)
> nss (nss)
> hunspell (hunspell)
> hyphen (hyphen)
> saxon (saxon)
> rhino (rhino)
> beanshell (beanshell)
> silgraphite (graphite)
>
>
> I have added (locally, not yet checked in) a flag (working
> title still is --{enable|disable}-category-b).
>
> When specified as --disable-category-b then all libraries
> are disabled. Switches for individual libraries
> override this.
>
> When specified as --enable-category-b then all libraries
> except seamonkey and nss are enabled. Again, switches
> for individual libraries override this.
>
> Seamonkey and nss are not enabled by this switch because of
> the large and complex set of switches available for these
> libraries. There is no simple on/off switch.
> More information is needed by configure to prepare building
> them.
>
> I am planning on testing this a bit more (especially to
> make builds on Linux and Mac; I am working mainly on
> Windows), decide on a name (suggestions still welcome), and
> check in my changes on Thursday or Friday (depending on how
> well testing goes).
>
> Best regards,
> Andre
>
Re: Configure and category B
Posted by Andre Fischer <af...@a-w-f.de>.
Hi all,
here is an update.
The following libraries have category B license, the modules in which
they are used in parentheses:
seamonkey (moz)
nss (nss)
hunspell (hunspell)
hyphen (hyphen)
saxon (saxon)
rhino (rhino)
beanshell (beanshell)
silgraphite (graphite)
I have added (locally, not yet checked in) a flag (working title still
is --{enable|disable}-category-b).
When specified as --disable-category-b then all libraries are disabled.
Switches for individual libraries override this.
When specified as --enable-category-b then all libraries except
seamonkey and nss are enabled. Again, switches for individual libraries
override this.
Seamonkey and nss are not enabled by this switch because of the large
and complex set of switches available for these libraries. There is no
simple on/off switch. More information is needed by configure to
prepare building them.
I am planning on testing this a bit more (especially to make builds on
Linux and Mac; I am working mainly on Windows), decide on a name
(suggestions still welcome), and check in my changes on Thursday or
Friday (depending on how well testing goes).
Best regards,
Andre
Re: Configure and category B
Posted by Andre Fischer <af...@a-w-f.de>.
On 09.12.2011 15:51, Rob Weir wrote:
> On Fri, Dec 9, 2011 at 8:03 AM, Oliver-Rainer Wittmann
> <or...@googlemail.com> wrote:
>> Hi,
>>
>>
>> On 09.12.2011 10:52, Raphael Bircher wrote:
>>>
>>> Am 09.12.11 10:46, schrieb Andre Fischer:
>>>>
>>>> Hi all,
>>>>
>>>> We are making good progress with removing category X licensed code (see
>>>> [1]).
>>>> On [2], first table, you can see, that most issues have been resolved,
>>>> the
>>>> remaining ones are being worked on.
>>>>
>>>> Therefore I will turn my attention to handling the category B (see [3])
>>>> code.
>>>> It is now part of the SVN repository and can be found as archives in the
>>>> top-level ext_sources/ directory.
>>>>
>>>> As far as I understand it, the category B code will not be part of a
>>>> source
>>>> release. It has to be checked out from SVN. The configure (.in) script
>>>> has to
>>>> be cleaned up so that category B code is not built by default but can be
>>>> activated with a single switch, similar to the current --enable-copyleft
>>>> switch.
>>>>
>>>> Does anybody have an idea for a name for the new switch better than
>>>> --enable-category-b ?
>>>
>>> --with-42 but this option should realy solve all problems ;-)
>>
>>
>> I like this one, but my proposal is:
>> --enable-weak-copyleft-components
>>
>
> Would it be feasible to have more granular flags, one for each
> category-b component? Or is it all-or-nothing?
The --enable-category-b is just a way to conveniently turn on/off the
category-B components. You can still override it with the already
existing flags for individual components. The most important change
will be to not enable any category B component by default.
By the way, I am still in the exploratory phase. It could well be that
instead of/additional to the --enable... switch we need an --allow...
switch and let the default values of the individual projects define
whether to enable them.
Also by the way, I have created issue 118674
(https://issues.apache.org/ooo/show_bug.cgi?id=118674) to track progress
on this.
-Andre
>
>
>> Best regards, Oliver.
Re: Configure and category B
Posted by Rob Weir <ro...@apache.org>.
On Fri, Dec 9, 2011 at 8:03 AM, Oliver-Rainer Wittmann
<or...@googlemail.com> wrote:
> Hi,
>
>
> On 09.12.2011 10:52, Raphael Bircher wrote:
>>
>> Am 09.12.11 10:46, schrieb Andre Fischer:
>>>
>>> Hi all,
>>>
>>> We are making good progress with removing category X licensed code (see
>>> [1]).
>>> On [2], first table, you can see, that most issues have been resolved,
>>> the
>>> remaining ones are being worked on.
>>>
>>> Therefore I will turn my attention to handling the category B (see [3])
>>> code.
>>> It is now part of the SVN repository and can be found as archives in the
>>> top-level ext_sources/ directory.
>>>
>>> As far as I understand it, the category B code will not be part of a
>>> source
>>> release. It has to be checked out from SVN. The configure (.in) script
>>> has to
>>> be cleaned up so that category B code is not built by default but can be
>>> activated with a single switch, similar to the current --enable-copyleft
>>> switch.
>>>
>>> Does anybody have an idea for a name for the new switch better than
>>> --enable-category-b ?
>>
>> --with-42 but this option should realy solve all problems ;-)
>
>
> I like this one, but my proposal is:
> --enable-weak-copyleft-components
>
Would it be feasible to have more granular flags, one for each
category-b component? Or is it all-or-nothing?
> Best regards, Oliver.
Re: Configure and category B
Posted by Oliver-Rainer Wittmann <or...@googlemail.com>.
Hi,
On 09.12.2011 10:52, Raphael Bircher wrote:
> Am 09.12.11 10:46, schrieb Andre Fischer:
>> Hi all,
>>
>> We are making good progress with removing category X licensed code (see [1]).
>> On [2], first table, you can see, that most issues have been resolved, the
>> remaining ones are being worked on.
>>
>> Therefore I will turn my attention to handling the category B (see [3]) code.
>> It is now part of the SVN repository and can be found as archives in the
>> top-level ext_sources/ directory.
>>
>> As far as I understand it, the category B code will not be part of a source
>> release. It has to be checked out from SVN. The configure (.in) script has to
>> be cleaned up so that category B code is not built by default but can be
>> activated with a single switch, similar to the current --enable-copyleft switch.
>>
>> Does anybody have an idea for a name for the new switch better than
>> --enable-category-b ?
> --with-42 but this option should realy solve all problems ;-)
I like this one, but my proposal is:
--enable-weak-copyleft-components
Best regards, Oliver.
Re: Configure and category B
Posted by Raphael Bircher <r....@gmx.ch>.
Am 09.12.11 10:46, schrieb Andre Fischer:
> Hi all,
>
> We are making good progress with removing category X licensed code
> (see [1]). On [2], first table, you can see, that most issues have
> been resolved, the remaining ones are being worked on.
>
> Therefore I will turn my attention to handling the category B (see
> [3]) code. It is now part of the SVN repository and can be found as
> archives in the top-level ext_sources/ directory.
>
> As far as I understand it, the category B code will not be part of a
> source release. It has to be checked out from SVN. The configure
> (.in) script has to be cleaned up so that category B code is not built
> by default but can be activated with a single switch, similar to the
> current --enable-copyleft switch.
>
> Does anybody have an idea for a name for the new switch better than
> --enable-category-b ?
--with-42 but this option should realy solve all problems ;-)
>
> Best regards,
> Andre
>
> [1] http://www.apache.org/legal/3party.html#category-x
> [2] https://cwiki.apache.org/confluence/display/OOOUSERS/IP_Clearance
> [3] http://www.apache.org/legal/3party.html#category-b
>
--
My private Homepage: http://www.raphaelbircher.ch/