You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Ariel Constenla-Haile <ar...@gmail.com> on 2011/10/04 17:27:28 UTC
GStreamer avmedia plugin as copyleft?
Hi there,
The GStreamer avmedia plugin is disabled when copyleft is disabled (the
default in AOOo).
http://svn.apache.org/viewvc/incubator/ooo/trunk/main/configure.in?view=markup#l1248
I cannot understand why this is treated as copy-left code. The plugin
was developed by Oracle and is on the software grant; building it only
requires system headers and linking against system libraries.
In this sense, the code is just like the VCL GTK and KDE plugins, and the GTK
and KDE file pickers... these are not disabled as copy-left code.
So, is this code copy-left code? Does building and shipping the pulgin
break some Apache licensing rule?
Regards
--
Ariel Constenla-Haile
La Plata, Argentina
Re: GStreamer avmedia plugin as copyleft?
Posted by RGB ES <rg...@gmail.com>.
2011/10/5 Andrea Pescetti <pe...@openoffice.org>
> On 04/10/2011 23:58 RGB ES wrote:
>
>> I can see a big problem coming: with every single Linux distro using LibO
>> for the foreseeable future and considering the fact that nobody will build
>> OOo at home (specially on windows), if, say, next year somebody install
>> OOo
>> 3.4 that will be for sure an Apache build.
>>
>
> I think that, when a new version of OpenOffice.org is released, most
> distributions will make OpenOffice.org available again in their
> repositories.
>
>
I'm not that optimist, sorry. As a matter of fact, I do not know a single
Linux distribution that ever distributed a vanilla OOo: since many years
Linux distributions used go-oo, and even that was heavily patched in many
cases.
Even now, with LibO delivering almost all the patches introduced by go-oo,
main Linux distros *patch LibO* in order to "add more features"... just look
at the terrible KDE4 "integration" offered by openSUSE.
Thanks to projects like the build service, maybe some users will start
personal repositories with OOo builds, but I'll not hold my breath until a
main Linux distro starts distributing OOo.
If an AOOo 3.4 binary is ever available for Linux, it will be because it was
built by Apache and offered on the AOO site.
Re: GStreamer avmedia plugin as copyleft?
Posted by Andrea Pescetti <pe...@openoffice.org>.
On 04/10/2011 23:58 RGB ES wrote:
> I can see a big problem coming: with every single Linux distro using LibO
> for the foreseeable future and considering the fact that nobody will build
> OOo at home (specially on windows), if, say, next year somebody install OOo
> 3.4 that will be for sure an Apache build.
I think that, when a new version of OpenOffice.org is released, most
distributions will make OpenOffice.org available again in their
repositories. Offering LibreOffice too is no problem: major
distributions have at least a dozen text editors, half a dozen e-mail
programs and three Office suites (OpenOffice.org or LibreOffice, KOffice
or derivatives and Abiword+Gnumeric). Offering both OpenOffice.org and
LibreOffice will be just normal.
> compiled with no switches, that will mean that every person downloading and
> installing OOo 3.4 will find an office suite not only without multimedia
> support, but also without spell checker!
When they package OpenOffice.org, distributions will make sure to use
the right switches to benefit from other packages installed in the
system and to offer better integration. This is what happens now for
virtually all distributions shipping OpenOffice.org or LibreOffice, so,
like Pedro wrote, I don't expect big problems here.
Regards,
Andrea.
Re: GStreamer avmedia plugin as copyleft?
Posted by Pedro Giffuni <pf...@apache.org>.
--- On Tue, 10/4/11, RGB ES <rg...@gmail.com> wrote:
...
>
> Sorry for jumping into the discussion ;)
> I can see a big problem coming: with every single Linux
> distro using LibO for the foreseeable future and
> considering the fact that nobody will build
> OOo at home (specially on windows), if, say, next year
> somebody install OOo 3.4 that will be for sure an Apache
> build. But if that Apache build is compiled with no
> switches, that will mean that every person downloading
> and installing OOo 3.4 will find an office suite not only
> without multimedia support, but also without spell checker!
I can only speak for the FreeBSD port but that won't happen.
What will happen is that both LO and AOO will share a lot of
binary components including the spell checker. Most of the
stuff that we need to kick out has been already kicked out
in LibreOffice, we just have to teach configure to find them.
> IMHO, that will be a very, very bad move that will create
> tons of negative reactions.
> I'm just a plain user so I do have any idea how to solve
> this problem, but I believe a discussion about this issue
> should be a priority.
For people building distributions I think it's in their
best interest to include all the features they can, so
I am sure they will take the time to do it. I can see
that some of them will also take the chance to add
malware but that will happen in LO too just as it
happens in VLC, etc.
cheers,
Pedro.
Re: GStreamer avmedia plugin as copyleft?
Posted by RGB ES <rg...@gmail.com>.
2011/10/4 Mathias Bauer <Ma...@gmx.net>
> Am 04.10.2011 17:27, schrieb Ariel Constenla-Haile:
>
> > Hi there,
> >
> > The GStreamer avmedia plugin is disabled when copyleft is disabled (the
> > default in AOOo).
> >
> http://svn.apache.org/viewvc/incubator/ooo/trunk/main/configure.in?view=markup#l1248
> > I cannot understand why this is treated as copy-left code. The plugin
> > was developed by Oracle and is on the software grant; building it only
> > requires system headers and linking against system libraries.
> > In this sense, the code is just like the VCL GTK and KDE plugins, and the
> GTK
> > and KDE file pickers... these are not disabled as copy-left code.
> >
> > So, is this code copy-left code? Does building and shipping the pulgin
> > break some Apache licensing rule?
> >
> > Regards
>
> The GStreamer integration doesn't make sense without GStreamer - so we
> shouldn't build it when no GStreamer libs are available.
>
> We decided that configure without switches should be the default Apache
> build. OTOH we didn't agree on linking against lgpl libraries in the
> system in this default build, so I disabled GStreamer by default (as
> well as some other copyleft components - there is no difference in that
> regard between GStreamer and hunspell!). This is an open question that
> IIRC I already asked here on that list (at least I wanted to do that ;-)).
>
> If we decided that linking against LGPL libs installed in the local
> system is OK for a "vanilla Apache" build, we could enable e.g.
> GStreamer on Linux again, but then we also could enable Hunspell and the
> other stuff that are disabled when "copyleft" stuff isn't enabled
> explicitly. Until then you have to use "--with-system..." switches to
> enable these copyleft components. If that doesn't work - you have found
> a bug. :-)
>
> Does that make sense?
>
> Regards,
> Mathias
>
Sorry for jumping into the discussion ;)
I can see a big problem coming: with every single Linux distro using LibO
for the foreseeable future and considering the fact that nobody will build
OOo at home (specially on windows), if, say, next year somebody install OOo
3.4 that will be for sure an Apache build. But if that Apache build is
compiled with no switches, that will mean that every person downloading and
installing OOo 3.4 will find an office suite not only without multimedia
support, but also without spell checker!
IMHO, that will be a very, very bad move that will create tons of negative
reactions.
I'm just a plain user so I do have any idea how to solve this problem, but I
believe a discussion about this issue should be a priority.
Regards
Ricardo
Re: GStreamer avmedia plugin as copyleft?
Posted by Mathias Bauer <ma...@numberfour.eu>.
On 05.10.2011 02:34, Ariel Constenla-Haile wrote:
> It seems the question remains if vanilla AOOo can link against copy-left
> system libraries.
Exactly. And moreover, which libraries can be named "system" libraries.
IMHO gtk can, but librsvg can't. Don't know about GStreamer.
Regards,
Mathias
Re: GStreamer avmedia plugin as copyleft?
Posted by Ariel Constenla-Haile <ar...@gmail.com>.
Hello Mathias,
On Tue, Oct 04, 2011 at 11:28:06PM +0200, Mathias Bauer wrote:
> Am 04.10.2011 17:27, schrieb Ariel Constenla-Haile:
>
> > Hi there,
> >
> > The GStreamer avmedia plugin is disabled when copyleft is disabled (the
> > default in AOOo).
> > http://svn.apache.org/viewvc/incubator/ooo/trunk/main/configure.in?view=markup#l1248
> > I cannot understand why this is treated as copy-left code. The plugin
> > was developed by Oracle and is on the software grant; building it only
> > requires system headers and linking against system libraries.
> > In this sense, the code is just like the VCL GTK and KDE plugins, and the GTK
> > and KDE file pickers... these are not disabled as copy-left code.
> >
> > So, is this code copy-left code? Does building and shipping the pulgin
> > break some Apache licensing rule?
> >
> > Regards
>
> The GStreamer integration doesn't make sense without GStreamer - so we
> shouldn't build it when no GStreamer libs are available.
of course it does not make sense a GStreamer integration without
GStreamer, but OOo never shipped its own GStremer libraries, just like
OOo never shipped its own gtk libs for the VCL gtk plugin, nor Qt3/KDE3
libs for the VCL kde plugin (Qt4/KDE4 was never built by Hamburg, IIRC
pl made a cws for that).
So building the plugins was decided by configure when libs were
available on the system (I guess Hamburg built on Linux system with gtk and
kde3 libraries - kde4 was never built).
> We decided that configure without switches should be the default Apache
> build. OTOH we didn't agree on linking against lgpl libraries in the
> system in this default build, so I disabled GStreamer by default (as
> well as some other copyleft components - there is no difference in that
> regard between GStreamer and hunspell!).
IMHO there is a difference, the GStreamer case should be placed together
with gtk and Qt/KDE integration, see below.
> This is an open question that
> IIRC I already asked here on that list (at least I wanted to do that ;-)).
following this, we should also disable the vcl plugins; that is
a vanilla AOOo without Linux Desktop integration! A no-go, of course...
> If we decided that linking against LGPL libs installed in the local
> system is OK for a "vanilla Apache" build, we could enable e.g.
> GStreamer on Linux again, but then we also could enable Hunspell and the
> other stuff that are disabled when "copyleft" stuff isn't enabled
> explicitly.
I think we should make a difference here between Linux-only features and
multi-platform ones.
GStreamer, VCL gtk plugin, VCL kde plugins, gtk/kde filepickers always linked
against system libraries, and it was never intended to ship own versions of
gtk/Qt/kde/GStreamer.
In these Linux specific cases, we do not face the problem of finding
alternatives because Apache only ships software with an Apache
compatible license: OOo (and now AOOo) will never ship its own copies of
GStreamer, gtk, Qt nor KDE.
The Hunspell case is different, because it would be possible to link
against Hunspell libs on Linux systems, but AFAIK this is not possible on
Windows.
> Until then you have to use "--with-system..." switches to
> enable these copyleft components.
there was never a --with-system-qt|kde|gtk and it makes no sense to have
a --with-system-gstreamer.
It looks like GStreamer, gtk, Qt/KDE integration should be treated
different from other copy-left components that AOOo is supposed to ship,
because it will always links against system libraries, not ship its own
copies.
It seems the question remains if vanilla AOOo can link against copy-left
system libraries.
Regards
--
Ariel Constenla-Haile
La Plata, Argentina
RE: GStreamer avmedia plugin as copyleft?
Posted by "Dennis E. Hamilton" <de...@acm.org>.
Enlightenment is an interesting project.
Although many of its sub-projects use the simple 2-point BSD license, there are some with LGPL and some unique licenses (i.e., one BSD-like that requires source-code to be made available).
I didn't make an exhaustive search.
- Dennis
[who is only mildly curious what an X11-based OO.o build would be like on Microsoft Windows. Enlightenment seems like a stretch though.]
-----Original Message-----
From: Pedro Giffuni [mailto:pfg@apache.org]
Sent: Wednesday, October 05, 2011 08:03
To: ooo-dev@incubator.apache.org; Jürgen Schmidt
Subject: Re: GStreamer avmedia plugin as copyleft?
http://www.enlightenment.org/
cheers,
Pedro.
--- On Wed, 10/5/11, Jürgen Schmidt <jo...@googlemail.com> wrote:
This was a subject I didn't want to bring in just yet, but
if it does happen that linking them is an issue, there are
replacements.
replacements? Really, what do you have in mind?
Juergen
Re: GStreamer avmedia plugin as copyleft?
Posted by Michael Stahl <ms...@openoffice.org>.
On 05.10.2011 09:42, Jürgen Schmidt wrote:
> On Wed, Oct 5, 2011 at 4:53 AM, Pedro Giffuni <pf...@apache.org> wrote:
>
>>
>> --- On Tue, 10/4/11, Ariel Constenla-Haile wrote:
>> ...
>>>
>>> it seems you miss my point here.
>>> If you disable building and shipping GStreamer because it
>>> links against copy-left system libs, then you should
>>> remove the VCL plugins too (AFAIK gtk is LGPL, I'm not
>>> sure about Qt/KDE).
>>>
>>
>> Oh .. indeed GTK++ and Qt are LGPL, but one of our mentors
>> said in the early days of this list that those could be
>> considered part of the system, so we can side step them ...
>> for now.
>>
>> This was a subject I didn't want to bring in just yet, but
>> if it does happen that linking them is an issue, there are
>> replacements.
>>
>>
> replacements? Really, what do you have in mind?
how about the venerable X Athena Widgets (Xaw)?
licensed under MIT X11, not contaminated with evil copyleft code, so it
should meet even the ASF's high licensing standards.
http://www.efalk.org/Widgets/Xaw.gif
i think there is even a 3D variant of it...
for a more modern look perhaps Motif could be considered, but
unfortunately there don't seem to be any permissively licensed variants
thereof (Lesstif is also contaminated with that eeevil copyleft stuff, and
"OpenMotif" isn't even open source!).
SCNR,
michael
Re: GStreamer avmedia plugin as copyleft?
Posted by Pedro Giffuni <pf...@apache.org>.
http://www.enlightenment.org/
cheers,
Pedro.
--- On Wed, 10/5/11, Jürgen Schmidt <jo...@googlemail.com> wrote:
This was a subject I didn't want to bring in just yet, but
if it does happen that linking them is an issue, there are
replacements.
replacements? Really, what do you have in mind?
Juergen
Re: GStreamer avmedia plugin as copyleft?
Posted by Jürgen Schmidt <jo...@googlemail.com>.
On Wed, Oct 5, 2011 at 4:53 AM, Pedro Giffuni <pf...@apache.org> wrote:
>
> --- On Tue, 10/4/11, Ariel Constenla-Haile wrote:
> ...
> >
> > it seems you miss my point here.
> > If you disable building and shipping GStreamer because it
> > links against copy-left system libs, then you should
> > remove the VCL plugins too (AFAIK gtk is LGPL, I'm not
> > sure about Qt/KDE).
> >
>
> Oh .. indeed GTK++ and Qt are LGPL, but one of our mentors
> said in the early days of this list that those could be
> considered part of the system, so we can side step them ...
> for now.
>
> This was a subject I didn't want to bring in just yet, but
> if it does happen that linking them is an issue, there are
> replacements.
>
>
replacements? Really, what do you have in mind?
Juergen
Re: GStreamer avmedia plugin as copyleft?
Posted by Pedro Giffuni <pf...@apache.org>.
--- On Tue, 10/4/11, Ariel Constenla-Haile wrote:
...
>
> it seems you miss my point here.
> If you disable building and shipping GStreamer because it
> links against copy-left system libs, then you should
> remove the VCL plugins too (AFAIK gtk is LGPL, I'm not
> sure about Qt/KDE).
>
Oh .. indeed GTK++ and Qt are LGPL, but one of our mentors
said in the early days of this list that those could be
considered part of the system, so we can side step them ...
for now.
This was a subject I didn't want to bring in just yet, but
if it does happen that linking them is an issue, there are
replacements.
Pedro.
Re: GStreamer avmedia plugin as copyleft?
Posted by Ariel Constenla-Haile <ar...@gmail.com>.
Hi Pedro,
On Tue, Oct 04, 2011 at 06:16:01PM -0700, Pedro Giffuni wrote:
> > but we are talking here about the GStreamer *plugin*. Just
> > like the gtk and kde VLC plugins, they have Oracle license,
> > and they are in the software grant, this means they (will)
> > have Apache License.
> >
>
> We can ship the AL2 source code and people can find
> out what to do with them but we cannot ship them in a
> binary release because they require linking to LGPL stuff.
is this true? can't the shipped binaries link against copy-left
system libraries?
> Of course, a linux/BSD distribution can but it cannot be
> mandatory.
>
> Alternatively we can AL2+LGPL code and binaries in
> apache-extras, and this would make sense if the plugins
> can be abstracted.
>
> > If AOOo will build a vanilla Linux version it should be
> > shipped with the gtk and kde plugins (no desktop
> > integration is a no-go!).
>
> I think pulling stuff out of the main distribution
> actually makes sense: OOo is very big and it has a
> lots of features that most people don't need.
> gstreamer is one of those cases: I personally don't
> use it so spending time and disk space building it
> is not very motivating but a flexible gstreamer
> plugin would be great for people that do use it.
it seems you miss my point here.
If you disable building and shipping GStreamer because it links
against copy-left system libs, then you should remove the VCL
plugins too (AFAIK gtk is LGPL, I'm not sure about Qt/KDE).
Removing the VCL plugins is shipping an AOOo that looks like:
~]$ export SAL_USE_VCLPLUGIN="gen";export OOO_FORCE_DESKTOP="none"
~]$ /opt/openoffice.org3/program/soffice
a no-go, IMHO.
Regards
--
Ariel Constenla-Haile
La Plata, Argentina
Re: GStreamer avmedia plugin as copyleft?
Posted by Jürgen Schmidt <jo...@googlemail.com>.
On Thu, Oct 6, 2011 at 10:09 AM, Alexander Thurgood <alex.thurgood@gmail.com
> wrote:
> Le 05/10/11 21:07, Mathias Bauer a écrit :
>
> Hi Mathias,
>
> >
> > Of course that would probably mean that our Linux version won't run out
> > of the box on most Linux machines as the old OOo version did. It will
> > run only on those computers that have compatible versions of all
> > libraries installed in their system that were used in the build. That's
> > the price you have to pay.
>
> Indeed, as I recently found out when I built the MysQL Connector
> extension against Ubuntu's mysqlcppconnector library :-/ It appears that
> the extension is not only arch specific, but also dist-version specific,
> at least as far as I can tell from my preliminary investigations. I
> haven't yet tried building with the basic mysql C library, that will be
> my next step.
>
> Dependency hell, here we come :-))
>
the used baseline for vanilla OOo builds was not bad from this perspective.
Ideally would be if we can reach a point where Linux distros will take the
sources of AOO, build it and include it in their distro directly. A
potential remaining problem will be C++ extensions that are not directly
included or available via the distro specific package manager.
The platform dependency of C++ extensions is one reason why i prefer Java
for extensions. It's much easier to maintain and to distribute via an
extension repository. And the development is also easier because you need
only an office and the SDK.
Juergen
Re: GStreamer avmedia plugin as copyleft?
Posted by Alexander Thurgood <al...@gmail.com>.
Le 05/10/11 21:07, Mathias Bauer a écrit :
Hi Mathias,
>
> Of course that would probably mean that our Linux version won't run out
> of the box on most Linux machines as the old OOo version did. It will
> run only on those computers that have compatible versions of all
> libraries installed in their system that were used in the build. That's
> the price you have to pay.
Indeed, as I recently found out when I built the MysQL Connector
extension against Ubuntu's mysqlcppconnector library :-/ It appears that
the extension is not only arch specific, but also dist-version specific,
at least as far as I can tell from my preliminary investigations. I
haven't yet tried building with the basic mysql C library, that will be
my next step.
Dependency hell, here we come :-))
Alex
Re: GStreamer avmedia plugin as copyleft?
Posted by Mathias Bauer <ma...@numberfour.eu>.
On 05.10.2011 02:46, Ariel Constenla-Haile wrote:
> On Tue, Oct 04, 2011 at 03:12:09PM -0700, Pedro Giffuni wrote:
>>> The GStreamer integration doesn't make sense without
>>> GStreamer - so we
>>> shouldn't build it when no GStreamer libs are available.
>>>
>>
>> Agreed.
>>
>>> We decided that configure without switches should be the
>>> default Apache build. OTOH we didn't agree on linking
>>> against lgpl libraries in the system in this default
>>> build, so I disabled GStreamer by default (as
>>> well as some other copyleft components - there is no
>>> difference in that regard between GStreamer and hunspell!).
>>
>> There is a *huge* difference here: Hunspell is MPL so we can
>> use it. LGPL is category X: we can't use Gstreamer at at.
>>
>> We can keep the MPL stuff around but anything GPL we should
>> consider extensions and move to apache-extras. The glue code
>> that we can relicense to AL2 we will, of course.
>
> but we are talking here about the GStreamer *plugin*. Just like the gtk
> and kde VLC plugins, they have Oracle license, and they are in the
> software grant, this means they (will) have Apache License.
>
> If AOOo will build a vanilla Linux version it should be shipped with the
> gtk and kde plugins (no desktop integration is a no-go!). Following this
> argument, it should also ship the GStreamer integration (here going back
> to the Java Media Framework is a no-go!).
The difference is that you can safely assume that one of the vcl plugins
will work on the user's computer without urging him to install
additional packages. That's not true for GStreamer.
The GStreamer plugin can't even be compiled without GStreamer libraries
installed. Of course you can use them installed in your system, but - as
I wrote - so far we didn't agree that this should be allowed in a
Vanilla build. So the correct way to build with GStreamer from the
system is using "--with-system-GStreamer" or so (don't know if this
switch exists already). Without any switch we must assume that the
GStreamer lib is not available and so we can't compile the plugin.
As soon as we have an agreement that building against system libs is OK
for a Vanilla AOOo build , we can compile much more stuff in OOo on
Linux, most probably nearly every copyleft component we had to disable
otherwise.
Of course that would probably mean that our Linux version won't run out
of the box on most Linux machines as the old OOo version did. It will
run only on those computers that have compatible versions of all
libraries installed in their system that were used in the build. That's
the price you have to pay.
Regards,
Mathias
Re: GStreamer avmedia plugin as copyleft?
Posted by Pedro Giffuni <pf...@apache.org>.
--- On Tue, 10/4/11, Ariel Constenla-Haile
>
> but we are talking here about the GStreamer *plugin*. Just
> like the gtk and kde VLC plugins, they have Oracle license,
> and they are in the software grant, this means they (will)
> have Apache License.
>
We can ship the AL2 source code and people can find
out what to do with them but we cannot ship them in a
binary release because they require linking to LGPL stuff.
Of course, a linux/BSD distribution can but it cannot be
mandatory.
Alternatively we can AL2+LGPL code and binaries in
apache-extras, and this would make sense if the plugins
can be abstracted.
> If AOOo will build a vanilla Linux version it should be
> shipped with the gtk and kde plugins (no desktop
> integration is a no-go!).
I think pulling stuff out of the main distribution
actually makes sense: OOo is very big and it has a
lots of features that most people don't need.
gstreamer is one of those cases: I personally don't
use it so spending time and disk space building it
is not very motivating but a flexible gstreamer
plugin would be great for people that do use it.
Pedro.
Re: GStreamer avmedia plugin as copyleft?
Posted by Ariel Constenla-Haile <ar...@gmail.com>.
On Tue, Oct 04, 2011 at 03:12:09PM -0700, Pedro Giffuni wrote:
> > The GStreamer integration doesn't make sense without
> > GStreamer - so we
> > shouldn't build it when no GStreamer libs are available.
> >
>
> Agreed.
>
> > We decided that configure without switches should be the
> > default Apache build. OTOH we didn't agree on linking
> > against lgpl libraries in the system in this default
> > build, so I disabled GStreamer by default (as
> > well as some other copyleft components - there is no
> > difference in that regard between GStreamer and hunspell!).
>
> There is a *huge* difference here: Hunspell is MPL so we can
> use it. LGPL is category X: we can't use Gstreamer at at.
>
> We can keep the MPL stuff around but anything GPL we should
> consider extensions and move to apache-extras. The glue code
> that we can relicense to AL2 we will, of course.
but we are talking here about the GStreamer *plugin*. Just like the gtk
and kde VLC plugins, they have Oracle license, and they are in the
software grant, this means they (will) have Apache License.
If AOOo will build a vanilla Linux version it should be shipped with the
gtk and kde plugins (no desktop integration is a no-go!). Following this
argument, it should also ship the GStreamer integration (here going back
to the Java Media Framework is a no-go!).
Regards
--
Ariel Constenla-Haile
La Plata, Argentina
Re: GStreamer avmedia plugin as copyleft?
Posted by Pedro Giffuni <pf...@apache.org>.
--- On Tue, 10/4/11, Mathias Bauer <Ma...@gmx.net> wrote:
...
>
> The GStreamer integration doesn't make sense without
> GStreamer - so we
> shouldn't build it when no GStreamer libs are available.
>
Agreed.
> We decided that configure without switches should be the
> default Apache build. OTOH we didn't agree on linking
> against lgpl libraries in the system in this default
> build, so I disabled GStreamer by default (as
> well as some other copyleft components - there is no
> difference in that regard between GStreamer and hunspell!).
There is a *huge* difference here: Hunspell is MPL so we can
use it. LGPL is category X: we can't use Gstreamer at at.
We can keep the MPL stuff around but anything GPL we should
consider extensions and move to apache-extras. The glue code
that we can relicense to AL2 we will, of course.
> This is an open question that
> IIRC I already asked here on that list (at least I wanted
> to do that ;-)).
>
There are bigger issues... but I'll keep them for later :-).
>
> Does that make sense?
>
One other thing ... we have to move-in the patch to use
COIN-OR to replace lp_solve. The COIN-OR stuff originated
(mostly) in IBM and is under CPL/EPL. We can treat it as
if it were MPL but help from the IBM guys to relicense it
to AL2 is welcome! (a SGA would be just fine, of course ;) )
In any case, and here I show my ignorance in OOo inner
workings, I hope we can make the coin-lp solver compatible
with the older lp_solve plugin here:
http://code.google.com/p/scsolver/
cheers,
Pedro.
Re: GStreamer avmedia plugin as copyleft?
Posted by Mathias Bauer <Ma...@gmx.net>.
Am 04.10.2011 17:27, schrieb Ariel Constenla-Haile:
> Hi there,
>
> The GStreamer avmedia plugin is disabled when copyleft is disabled (the
> default in AOOo).
> http://svn.apache.org/viewvc/incubator/ooo/trunk/main/configure.in?view=markup#l1248
> I cannot understand why this is treated as copy-left code. The plugin
> was developed by Oracle and is on the software grant; building it only
> requires system headers and linking against system libraries.
> In this sense, the code is just like the VCL GTK and KDE plugins, and the GTK
> and KDE file pickers... these are not disabled as copy-left code.
>
> So, is this code copy-left code? Does building and shipping the pulgin
> break some Apache licensing rule?
>
> Regards
The GStreamer integration doesn't make sense without GStreamer - so we
shouldn't build it when no GStreamer libs are available.
We decided that configure without switches should be the default Apache
build. OTOH we didn't agree on linking against lgpl libraries in the
system in this default build, so I disabled GStreamer by default (as
well as some other copyleft components - there is no difference in that
regard between GStreamer and hunspell!). This is an open question that
IIRC I already asked here on that list (at least I wanted to do that ;-)).
If we decided that linking against LGPL libs installed in the local
system is OK for a "vanilla Apache" build, we could enable e.g.
GStreamer on Linux again, but then we also could enable Hunspell and the
other stuff that are disabled when "copyleft" stuff isn't enabled
explicitly. Until then you have to use "--with-system..." switches to
enable these copyleft components. If that doesn't work - you have found
a bug. :-)
Does that make sense?
Regards,
Mathias