From: Drake Wyrm <wyrm@haell.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Installing COPYING or LICENSE files
Date: Mon, 26 Dec 2005 05:57:09 -0800 [thread overview]
Message-ID: <20051226135709.GB12305@phaenix.haell.com> (raw)
In-Reply-To: <43AFEF18.8020403@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1405 bytes --]
Petteri R??ty <betelgeuse@gentoo.org> wrote:
> Petteri R??ty wrote:
> > R Hill wrote:
> >>Daniel Ahlberg wrote:
> >>>* if ebuild installs COPYING and/or INSTALL into doc.
> >>
> >>Is this actually important? There are a hell of a lot of ebuilds that fail
> >>under this rule. I'd like to start filing patches for some of the packages in
> >>this list so I'm interested in knowing what's worth fixing and what's being
> >>pedantic.
> >
> > Not a blocker but just useless. Filing patches for ebuilds doing this is
> > greatly appreciated by at least me.
>
> https://bugs.gentoo.org/show_bug.cgi?id=113680
>
> So is there a policy about [not] installing the COPYING or LICENSE files
> already? If there isn't one, I propose we make a decision about this to
> have uniform behaviour across the tree.
You're going to be hard-pressed to get any kind of consensus on this
issue. Many dev seems to feel that the license belongs there. In some
cases the COPYING, LICENSE, and/or INSTALL files contain, not boilerplate
drivel, but actually unique, useful information.
Certainly there could be value in leaving out _yet_another_ copy of the
GPL and the banal INSTALL, but even that wouldn't justify a universal
ban on certain file names.
--
In the depths of my heart, I can't help being convinced
that my fellow men, with a few exceptions, are worthless.
-- Sigmund Freud
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2005-12-26 13:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-14 7:12 [gentoo-dev] aging ebuilds with unstable keywords Daniel Ahlberg
2005-11-14 13:14 ` Andrej Kacian
2005-11-21 2:39 ` [gentoo-dev] " R Hill
2005-11-21 12:47 ` Petteri Räty
2005-12-26 13:24 ` [gentoo-dev] Installing COPYING or LICENSE files Petteri Räty
2005-12-26 13:57 ` Drake Wyrm [this message]
2005-12-26 14:02 ` Petteri Räty
2005-12-26 14:12 ` Diego 'Flameeyes' Pettenò
2005-12-26 14:21 ` Carsten Lohrke
2005-12-27 7:01 ` [gentoo-dev] " R Hill
2005-12-27 7:08 ` Mike Frysinger
2005-12-27 7:23 ` Brian Harring
2005-12-27 7:33 ` Mike Frysinger
2005-12-27 13:14 ` Carsten Lohrke
2005-12-27 8:53 ` Harald van Dijk
2005-12-27 10:32 ` Petteri Räty
2005-12-27 11:20 ` Harald van Dijk
2005-12-27 14:57 ` Henrik Brix Andersen
2005-12-27 13:40 ` Harald van Dijk
2005-12-26 20:48 ` [gentoo-dev] " Mike Frysinger
2005-12-27 13:43 ` Petteri Räty
2005-11-25 7:16 ` [gentoo-dev] Re: aging ebuilds with unstable keywords Andrej Kacian
2005-11-25 23:15 ` R 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=20051226135709.GB12305@phaenix.haell.com \
--to=wyrm@haell.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