Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Jon Lech Johansen <jon@...>
Subject: avifile ebuild requires divx4linux and win32codecs on x86
Date: Thu, 24 Apr 2003 19:17:49 +0200
>From media-video/avifile/avifile-0.7.34.20030319.ebuild:

x86? ( >=media-libs/divx4linux-20020418
       >=media-libs/win32codecs-0.90 )

Requiring these is bad for two reasons:

1. Both divx4linux and win32codecs consist of closed source software.

2. win32codecs ebuild consists of WMP, QT and other codecs which are 
downloaded from mplayer's website. AFAIK the mplayer team has not
obtained a redistribution license from either Microsoft or Apple,
which makes their distribution a violation of copyright law. Their
website is located in Hungary, which is a member state of WIPO (whose
treaties are the basis for most copyright laws around the world). 

Providing the win32codecs ebuild could be considered contributory 
copyright infringement.

-- 
Jon Lech Johansen
jon@...
nanocrew.net/blog/

Stat sua cuique dies, breve et inreparabile tempus
omnibus est vitae; sed famam extendere factis,
hoc virtutis opus.

--
gentoo-dev@g.o mailing list

Replies:
Re: avifile ebuild requires divx4linux and win32codecs on x86
-- Bartosch Pixa
Re: avifile ebuild requires divx4linux and win32codecs on x86
-- Paul de Vrieze
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
RFC: deprecating kxicq2, kpopper
Next by thread:
Re: avifile ebuild requires divx4linux and win32codecs on x86
Previous by date:
Re: Fw: [gentoo-user] Gentoo's trouble with /bin/sh
Next by date:
Call for maintainers - sendmail


Updated Jun 17, 2009

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.