public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ricardo Loureiro <rjlouro@rjlouro.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev]  Re: RFC - Gentoo on the Lab
Date: Mon, 22 Aug 2005 14:26:58 +0100	[thread overview]
Message-ID: <20050822142658.0f5f7aab@acme.rjlouro.org> (raw)
In-Reply-To: <pan.2005.08.22.11.31.08.492258@cox.net>

[-- Attachment #1: Type: text/plain, Size: 1178 bytes --]

On Mon, 22 Aug 2005 04:31:09 -0700
Duncan <1i5t5.duncan@cox.net> wrote:

> Of course, the other possibility, if the permissiveness of BSD is
> desired,
> would be a dual-license BSD/GPL.  That clears up any possible
> conflicts
> directly and immediately.  OTOH, with portage itself already GPL2
> licensed, I'm not sure I see much point in BSD licensing any portage
> dependent new code, in any case, since it's dependent on GPL2 code
> anyway.
> Still, the dual license certainly can't harm, and would likely be my
> choice if I wanted the BSD permissiveness to apply to my code,
> under the
> circumstances.  (FWIW, I prefer GPL, so there's no question that's
> how I'd
> license it if it were me, but it's not, so that doesn't count.)
> 

BSD licence allows any fork to be created with any other licence, so
a BSD project can have a GPL fork. I didn't thought about changing
Portage itself simply because I don't know if the changes are welcome
to Gentoo itself, probably more a Gentoo server project. But if that
is a possibility I have no problems with GPL.


Ricardo Loureiro
--
http://pgp.dei.uc.pt:11371/pks/lookup?op=get&search=0x6B7C0EC0

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-08-22 13:30 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-22  1:58 [gentoo-dev] RFC - Gentoo on the Lab Ricardo Loureiro
2005-08-22  2:12 ` Andrew Gaffney
2005-08-22  3:34 ` Donnie Berkholz
2005-08-22 10:05   ` Ivan Yosifov
2005-08-22 11:31   ` [gentoo-dev] " Duncan
2005-08-22 13:26     ` Ricardo Loureiro [this message]
2005-08-22 23:57       ` [gentoo-dev] " Duncan
2005-08-22 14:38 ` [gentoo-dev] " Marius Mauch
2005-08-22 15:35   ` Ricardo Loureiro
2005-08-22 16:57     ` Grobian
2005-08-22 17:49   ` Kristian Benoit
2005-08-22 20:39     ` Brian Harring
2005-08-23 16:25       ` Kristian Benoit
2005-08-23 17:22         ` Brian Harring
2005-08-23 17:27         ` Brian Harring
2005-08-23 22:58           ` Kristian Benoit
2005-08-25  0:50             ` [gentoo-dev] portage rewrite snapshot (was RFC - Gentoo on the Lab) Brian Harring
2005-08-23 16:45       ` [gentoo-dev] RFC - Gentoo on the Lab Ricardo Loureiro
2005-08-22 20:41     ` Stephen Bennett
2005-08-23 16:28       ` Kristian Benoit
2005-08-23 17:19         ` Brian Harring
2005-08-23 16:34       ` Ricardo Loureiro
2005-08-23 17:28         ` Marius Mauch

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050822142658.0f5f7aab@acme.rjlouro.org \
    --to=rjlouro@rjlouro.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox