From: Michael Cummings <mcummings@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] GLEP 52 - GLEP 23 revisited
Date: Wed, 20 Sep 2006 10:05:00 -0400 [thread overview]
Message-ID: <1158761101.9521.8.camel@sys947.dtic.mil> (raw)
In-Reply-To: <451127AB.4060202@gentoo.org>
On Wed, 2006-09-20 at 13:36 +0200, Simon Stelling wrote:
> Every license which a package in the portage tree depends on gets a package in
> the ``txt-licenses/`` category. Its ebuild must install the license text to
> ``/usr/shared/licenses/``. The initial version shall be 1 if there is no version
> specified.
This doesn't make sense to me. I have a copy of every license used in
the portage tree already in /usr/portage/licenses - why dup that again?
We already have an existing LICENSE keywording in the ebuilds, why not
just focus on patching portage to allow a make.conf variable for allowed
licenses and block based on that?
--
-----o()o----------------------------------------------
Michael Cummings | #gentoo-dev, #gentoo-perl
Gentoo Perl Dev | on irc.freenode.net
Gentoo/SPARC
Gentoo/AMD64
GPG: 0543 6FA3 5F82 3A76 3BF7 8323 AB5C ED4E 9E7F 4E2E
-----o()o----------------------------------------------
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2006-09-20 14:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-20 11:36 [gentoo-dev] GLEP 52 - GLEP 23 revisited Simon Stelling
2006-09-20 13:09 ` Steev Klimaszewski
2006-09-20 13:21 ` Steev Klimaszewski
2006-09-20 13:22 ` Simon Stelling
2006-09-20 13:36 ` Krzysiek Pawlik
2006-09-20 13:51 ` Simon Stelling
2006-09-20 13:53 ` Brian Harring
2006-09-20 14:05 ` Michael Cummings [this message]
2006-09-20 16:03 ` Vlastimil Babka
2006-09-20 16:43 ` Kevin F. Quinn
2006-09-20 17:08 ` Mike Frysinger
2006-09-20 14:29 ` [gentoo-dev] " Duncan
2006-09-20 15:24 ` [gentoo-dev] " Luca Barbato
2006-09-20 16:18 ` Mike Frysinger
2006-09-20 16:36 ` Stephen Bennett
2006-09-20 17:34 ` Josh Saddler
2006-09-24 21:37 ` [gentoo-dev] " Ryan Hill
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=1158761101.9521.8.camel@sys947.dtic.mil \
--to=mcummings@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