License question.

qzm <[email protected]> Sat, 22 Aug 2009 00:16:43 +1200
Newsgroups gmane.comp.video.xvid.user
Message-ID <[email protected]>
--===============1718850910==
Content-Type: multipart/alternative; boundary=0016e64764d0666a470471a5d768

--0016e64764d0666a470471a5d768
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Please forgive me for asking a question that is likely to stir up some
disagreement, however I have been trying to track down an answer, or at
least someone who can answer - perhaps here is a good place.

The short version is that I am trying to clarify the restrictions on
providing the xvid codec as a binary installer (not in any way modified,
simply the current windows binary vfw codec linked from xvid.org) to some
users of my own (non GPL) software.

Now, that would of course be highly incorrect if my software required xvid
use, however the situation I am in is that some clients have other third
parties supplying them with xvid specific video files, and they complain to
me if these files will not work in my software - I point them at the
xvid.org site of course but not all situations are online computers - so
they ask me to supply the installer. I would rather not tell them to avoid
the files.

My software simply uses VfW/Directshow to access the files - however that of
course causes a loading of xvid for video that requires it (or a failure to
load the file..). I guess technically it comes down to the question of does
VfW/Directshow autoloading xvid constitute a linking or a seperate use - as
OS services are in the middle here outside my control (I do not even
know/care if the file requires xvid) I would err on the side of the second.

Reading the xvid FAQ it seems very strongly to state this is not allowable,
which does seem a touch surprising as by my understanding (and I know this
is often debated..) the aggregation clause of the GPL would allow me to make
the installer available alongside my application so long as my clients have
the choice to install it (or not), and I in no way modify it, its licenses,
or their presentation/function.

However, I of course do not wish to cross any lines, and have great respect
for the wishes of the xvid developers, so seek clarification.

I would love to get in touch with the license holder of xvid to ask
directly, however this is of course a difficult thing to achieve for any
such project.

Again, sorry if this is a poor place for this question, I would love to be
able to track down a more official contact for such questions.

http://www.xvid.org/FAQ.42.0.html#c44
http://www.gnu.org/licenses/gpl-faq.html#MereAggregation
http://forum.doom9.org/showthread.php?t=125721

--0016e64764d0666a470471a5d768
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Please forgive me for asking a question that is likely to stir up some disa=
greement, however I have been trying to track down an answer, or at least s=
omeone who can answer - perhaps here is a good place.<br><br>The short vers=
ion is that I am trying to clarify the restrictions on providing the xvid c=
odec as a binary installer (not in any way modified, simply the current win=
dows binary vfw codec linked from <a href=3D"http://xvid.org">xvid.org</a>)=
 to some users of my own (non GPL) software.<br>
<br>Now, that would of course be highly incorrect if my software required x=
vid use, however the situation I am in is that some clients have other thir=
d parties supplying them with xvid specific video files, and they complain =
to me if these files will not work in my software - I point them at the <a =
href=3D"http://xvid.org">xvid.org</a> site of course but not all situations=
 are online computers - so they ask me to supply the installer. I would rat=
her not tell them to avoid the files.<br>
<br>My software simply uses VfW/Directshow to access the files - however th=
at of course causes a loading of xvid for video that requires it (or a fail=
ure to load the file..). I guess technically it comes down to the question =
of does VfW/Directshow autoloading xvid constitute a linking or a seperate =
use - as OS services are in the middle here outside my control (I do not ev=
en know/care if the file requires xvid) I would err on the side of the seco=
nd.<br>
<br>Reading the xvid FAQ it seems very strongly to state this is not allowa=
ble, which does seem a touch surprising as by my understanding (and I know =
this is often debated..) the aggregation clause of the GPL would allow me t=
o make the installer available alongside my application so long as my clien=
ts have the choice to install it (or not), and I in no way modify it, its l=
icenses, or their presentation/function.<br>
<br>However, I of course do not wish to cross any lines, and have great res=
pect for the wishes of the xvid developers, so seek clarification.<br><br>I=
 would love to get in touch with the license holder of xvid to ask directly=
, however this is of course a difficult thing to achieve for any such proje=
ct.<br>
<br>Again, sorry if this is a poor place for this question, I would love to=
 be able to track down a more official contact for such questions.<br><br><=
a href=3D"http://www.xvid.org/FAQ.42.0.html#c44">http://www.xvid.org/FAQ.42=
.0.html#c44</a><br>
<a href=3D"http://www.gnu.org/licenses/gpl-faq.html#MereAggregation">http:/=
/www.gnu.org/licenses/gpl-faq.html#MereAggregation</a><br><a href=3D"http:/=
/forum.doom9.org/showthread.php?t=3D125721">http://forum.doom9.org/showthre=
ad.php?t=3D125721</a><br>
<br>

--0016e64764d0666a470471a5d768--

--===============1718850910==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xvid-users mailing list
[email protected]
http://list.xvid.org/mailman/listinfo/xvid-users

--===============1718850910==--