On 09.12.2011 15:51, Rob Weir wrote:
On Fri, Dec 9, 2011 at 8:03 AM, Oliver-Rainer Wittmann
<[email protected]> 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.
