On Fri, 17 Jun 2005 00:12:30 +0200 Torsten Veller <[EMAIL PROTECTED]> wrote:
> * Patrick Lauer <[EMAIL PROTECTED]>: > > On Wed, 2005-06-15 at 13:18 +0200, Torsten Veller wrote: > > > > > Why do we add a license to the licenses/ dir? > > > > Because there should be an easy way to find licenses? > > And you can do "emerge search foo", then read the license and decide > > wether you want to install foo. > > > > > And in addition: When should a license be added to licenses/ ? > > > > When at least one ebuild uses a license that is not already there? > > Ok, here is a license: <http://rafb.net/paste/results/j88sYC87.html> > I couldn't decide if this one is present already. > All i have checked are slightly different. Maybe someone knows ;) > > If it is not in licenses/, can someone suggest a name for this one? Looks like as-is. > > > There are over 3MB in nearly 500 files. How will those licenses be > > > classified if ACCEPT_LICENSES (GLEP 23) is implemented? > > I guess groups ... OSI approved, "free", commercial, ... > > Classification <-> groups, sure. > But how? How can this be done with 500 files? Who wants to do this? Personally I'd only make groups: needs user confirmation and doesn't need user confirmation, as those are the only ones that have a technical reason (and the former group already needs special treatment). At most also use external lists of licenses like OSI or FSF, but IMO it would be a bad idea to provide any set of "free" licenses or use other vague/ subjective limitations. Marius -- Public Key at http://www.genone.de/info/gpg-key.pub In the beginning, there was nothing. And God said, 'Let there be Light.' And there was still nothing, but you could see a bit better.
pgp8gLLyzYhFY.pgp
Description: PGP signature
