From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Questions about licenses
Date: Wed, 15 Jun 2005 15:06:46 -0400 [thread overview]
Message-ID: <1118862406.14164.38.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <623652d5050615113873104599@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1334 bytes --]
On Wed, 2005-06-15 at 18:38 +0000, Chris Bainbridge wrote:
> On 15/06/05, Maurice van der Pot <griffon26@gentoo.org> wrote:
> > On Wed, Jun 15, 2005 at 10:04:39AM -0400, Chris Gianelloni wrote:
> > > > > What about all these /usr/share/doc/*/COPYING* files? Are they
> > > > > necessary if all licenses are in licenses/ ?
> > > > See first point. You want to read the license _before_ installing stuff
>
> The obvious thing to do is to have a licenses package that install all
> of the licenses somewhere. If someone wants to check a license they
> emerge it first. /usr/portage/licenses does seem unnecessarily big for
> the portage tree.
Not really...
See, since emerge -s shows the license, it would mean that portage would
need to RDEPEND on the package. Because of this, everyone would have
the package anyway. That and it is much simpler to commit a single
license file to the tree when adding a package with a new license, then
it would be to download the license package tarball, unpack it,
increment the version number, copy your license in, repack it, upload it
to Gentoo's mirrors, wait for it to sync, update the license package in
the tree, wait for that to sync, then add your package.
--
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-06-15 19:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-15 11:18 [gentoo-dev] Questions about licenses Torsten Veller
2005-06-15 11:31 ` 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 [this message]
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=1118862406.14164.38.camel@cgianelloni.nuvox.net \
--to=wolf31o2@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