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: "Stuart Herbert" <stuart.herbert@...>
Subject: Re: GPL and Source code providing
Date: Wed, 28 Jun 2006 10:44:02 +0100
Hi,

On 6/28/06, Mivz <mivz@...> wrote:
> Hello,
>
> I have just read the following story, which scared me a bit:
>
> http://software.newsforge.com/article.pl?sid=06/06/23/1728205&tid=150
>
> Does this obligation, to provide your own source, also count for a none
> Gentoo developer making a overlay tree for one of his projects which is
> licensed under de GPL-2? Because that is a derived distro form Gentoo
> right?
> Would that mean that, if u write software using the portage system, that
> every package that is used by one of your own should be available from a
> server of your own?
> If, the developer should also provide it's own file server with all
> those packages, this would cause that every developer that wanted to
> make a overlay should be a Gentoo file mirror?
>
> Do my senses run wilde? Your just my imagination?
> Do I understand this right?
>
> Mivz

Questions on how the law affects Gentoo are best put to the Gentoo
Trustees, who have access to our lawyers.  They're the only people who
should be commenting on legal stuff like this.

Best regards,
Stu
-- 
gentoo-dev@g.o mailing list


References:
GPL and Source code providing
-- Mivz
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: GPL and Source code providing
Next by thread:
Re: GPL and Source code providing
Previous by date:
Re: GPL and Source code providing
Next by date:
Re: GPL and Source code providing


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.