From: Torsten Veller <tove@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] Questions about licenses
Date: Wed, 15 Jun 2005 13:18:10 +0200 [thread overview]
Message-ID: <87u0jzhnrh.fsf@veller.net> (raw)
Why do we add a license to the licenses/ dir?
And in addition: When should a license be added to licenses/ ?
Do we only add those licenses to define valid names for the LICENSE
variable?
There are over 3MB in nearly 500 files. How will those licenses be
classified if ACCEPT_LICENSES (GLEP 23) is implemented?
Does the language of the license matter? (selfhtml is in german)
Aren't MIT and MetaKit and ... the same license?
Aren't X11 and cdegood and JamesClark and ... the same license?
Should the licenses/ dir be cleaned?
(Should placeholders be used as in MIT?)
What about all these /usr/share/doc/*/COPYING* files? Are they
necessary if all licenses are in licenses/ ?
(Am i asking too many questions? Sorry, but i have the feeling that
this whole license stuff is not useful atm and i don't see how we
can deal with the great number of files in the future.)
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2005-06-15 11:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-15 11:18 Torsten Veller [this message]
2005-06-15 11:31 ` [gentoo-dev] Questions about licenses Krzysiek Pawlik
2005-06-15 11:39 ` Jon Portnoy
2005-06-15 12:00 ` Krzysiek Pawlik
2005-06-15 12:14 ` Jon Portnoy
2005-06-15 12:29 ` Krzysiek Pawlik
2005-06-15 14:02 ` Chris Gianelloni
2005-06-15 14:07 ` Krzysiek Pawlik
2005-06-15 11:44 ` Patrick Lauer
2005-06-15 14:04 ` Chris Gianelloni
2005-06-15 16:26 ` Maurice van der Pot
2005-06-15 18:38 ` Chris Bainbridge
2005-06-15 19:06 ` Chris Gianelloni
2005-06-16 22:12 ` [gentoo-dev] " Torsten Veller
2005-06-16 23:06 ` Marius Mauch
2005-06-17 10:09 ` Chris Bainbridge
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=87u0jzhnrh.fsf@veller.net \
--to=tove@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