From: Daniel Black <dragonheart@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] CAcert certificate distribution license to third parties (i.e. distributors like gentoo)
Date: Wed, 16 Dec 2009 23:26:29 +1100 [thread overview]
Message-ID: <200912162326.30038.dragonheart@gentoo.org> (raw)
In-Reply-To: <4B277ECA.3000608@gentoo.org>
[-- Attachment #1: Type: Text/Plain, Size: 2105 bytes --]
On Tuesday 15 December 2009 23:19:22 Richard Freeman wrote:
> On 12/15/2009 01:46 AM, Daniel Black wrote:
> > I did email the debian maintainer too. no response yet. They have
> > interactive builds though and I guess we do too now. Will be a royal pain
> > if every CA/software did the same thing.
>
> The last thing gentoo needs is interactive builds.
agree.
> I'd rather put a disclaimer in the handbook that when you install gentoo
> you bear the consequences of anything you do with it: if you're in a
> jurisdiction where software licenses are binding on those who use
> software then be sure to set ACCEPT_LICENSE accordingly, and all users
> should monitor the outputs of their builds for important notices.
sounds reasonable.
> If legal experts feel that the only thing that will work would be an
> interactive build, then we should:
I'm not sure it is. Its very early days of this license.
after reading this license without (or significantly less of) a headache i'm
thinking 1.4 2) "to advice the end-user of the NRP-DaL" refers to advising the
user that the license exists rather the text of it. Gentoo maintainers could
simple add the NRP-DaL to the LICENSE of the ebuild. Portage 2.2's requiring
the user add acceptable licenses to ACCEPT_LICENSE is probably sufficient.
> I'm generally in favor of including CACert by default, but if they're
> going to shoot themselves in the foot over licensing then that is their
> loss.
they aren't trying to they just don't know our issues. I did ask for wider
consultation and to be wary of clauses incompatible with distributors normal
operations.
> .. and I really don't see why CACert is pushing this either...
Clearing up a legal loop to allow distribution in a way that communicates the
NRP-DaL to the end-user. Their own page http://www.cacert.org/index.php?id=3
doesn't mention NRP-DaL either so as you can see, their are just progressing
with a few little bumps and inconsistencies like everyone else.
https://lists.cacert.org/wws/arc/cacert-board/2009-12/msg00080.html
Daniel
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-12-16 14:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-13 11:44 [gentoo-dev] CAcert certificate distribution license to third parties (i.e. distributors like gentoo) Daniel Black
2009-12-13 19:49 ` Robin H. Johnson
2009-12-14 12:15 ` Richard Freeman
2009-12-14 20:10 ` Robin H. Johnson
2009-12-15 1:44 ` Richard Freeman
2009-12-15 6:46 ` Daniel Black
2009-12-15 12:19 ` Richard Freeman
2009-12-16 12:26 ` Daniel Black [this message]
2010-06-27 1:02 ` [gentoo-dev] " Daniel Black
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=200912162326.30038.dragonheart@gentoo.org \
--to=dragonheart@gentoo.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