public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Vincent Launchbury <vincent@doublecreations.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Non-free software in Gentoo
Date: Tue, 29 Dec 2009 00:24:09 -0500	[thread overview]
Message-ID: <4B399279.2030709@doublecreations.com> (raw)
In-Reply-To: <4B386808.8070607@gentoo.org>

Rémi Cardona wrote:
> Unless people dedicate time and effort, ACCEPT_LICENSE is useless.

Well, I think an incomplete tool is better than no tool at all. Even
though it's far from perfect, I still found it very useful to create a
free system. I'm certainly interested in helping to improve it.

> I'd say this is probably better suited for gentoo-project, but it's
> probably ok to start here, to gauge interest :)

Thanks, I'll subscribe to gentoo-project also.


Jeremy Olexa wrote:
> File bugs mate. Licensing is not exactly clear to all users or devs.  As 
> can be seen here[1] for dos2unix. It sounds like you care in this area, 
> so get involved.

That looks like a great starting point, thanks. The bug you mentioned
has been fixed already!


Robin H. Johnson wrote:
> The COPYRIGHT file in dos2unix is actually a 2-clause BSD license. I've
> updated the ebuild suitably.

Thanks, much appreciated.

> File a bug with some ebuilds.

It looks like somebody already has. See
http://bugs.gentoo.org/show_bug.cgi?id=266157. I tested the latest
ebuild, and it worked fine (see comment #59.) What would have to be done
to get it in the main tree?

> A profile is not the answer here.
> An optional DEP block || ( media-fonts/corefonts ... ) where the other
> item does resolve using ACCEPT_LICENSES is what should be used.

I'll have to read through the devmanual, thanks for the pointer.

> In your case, I propose that we add one or more stacked groups, with an
> initial content as such...

I'll start working on expanding LIBRE-FREE-1 then. I assume a bug report
would be the correct place to suggest this when I've made a decent
start?




  parent reply	other threads:[~2009-12-29  5:25 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-28  5:36 [gentoo-dev] Non-free software in Gentoo Vincent Launchbury
2009-12-28  8:10 ` Rémi Cardona
2009-12-28 13:11   ` Nirbheek Chauhan
2009-12-29  8:59     ` Peter Volkov
2009-12-29  5:24   ` Vincent Launchbury [this message]
2009-12-29  9:02     ` Peter Volkov
2009-12-29 18:32       ` Robin H. Johnson
2009-12-29 23:17         ` Brian Harring
2009-12-28 11:21 ` Jeroen Roovers
2009-12-28 14:37 ` Jeremy Olexa
2009-12-28 18:56 ` Robin H. Johnson
2009-12-28 22:15   ` Richard Freeman
2009-12-28 22:53     ` Robin H. Johnson
2009-12-29  1:16       ` Richard Freeman
2009-12-30  0:52         ` Greg KH
2009-12-30 11:43           ` Richard Freeman
2009-12-31  4:51             ` Greg KH
2009-12-31  6:02               ` Harald van Dijk
2009-12-30  0:50 ` Greg KH
2009-12-30  2:42   ` Vincent Launchbury
2009-12-31  4:48     ` Greg KH
2009-12-31 12:30       ` Richard Freeman
2010-01-06  4:55       ` Vincent Launchbury
2010-01-06 18:57         ` Greg KH
2010-01-06 21:55           ` Harald van Dijk
2010-01-07  6:19             ` Vincent Launchbury
2010-01-07 14:37               ` Richard Freeman
2010-01-08  5:26               ` Greg KH
2010-01-08 15:48                 ` Richard Freeman

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=4B399279.2030709@doublecreations.com \
    --to=vincent@doublecreations.com \
    --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