Bug#633797: copyright-format: "with <keywords> exception" underspecified
> On Wed, Nov 16, 2011 at 09:31:05AM +0900, Charles Plessy wrote:
> > Is there a concrete example where we need to support multiple exceptions ?
> > If not, I propose to follow and document the current practice, which is to
> > support only one. This has the advantage that it will not be needed to
> > implement new functions in parsers, nor to correct copyright files.
Le Tue, Nov 15, 2011 at 06:08:25PM -0800, Steve Langasek a écrit :
> I have no objection to this for 1.0, provided we at the same time clarify
> that if more than one exception is in use, you need to use a custom
> shortname instead of an ORed or ANDed list of licenses.
> Is there a consensus for this position?
> I think for future versions of the standard, it's worth covering this case
> even if it's only a hypothetical; but there's no reason to hold up 1.0 for
> something that's going to require parser changes and isn't in use anywhere.
Le Wed, Nov 16, 2011 at 10:49:46AM +0700, Jonas Smedegaard a écrit :
> Above approach sounds reasonable to me. Seconded.
Le Wed, Nov 16, 2011 at 11:38:29AM +0100, Jakub Wilk a écrit :
Thanks everybody for your answers. Here is a proposed patch.
Tsurumi, Kanagawa, Japan
>From fdbd7829fd59d7329353f306d0297817d05d0251 Mon Sep 17 00:00:00 2001
From: Charles Plessy <firstname.lastname@example.org>
Date: Wed, 16 Nov 2011 19:55:12 +0900
Subject: [PATCH] Multiple license exceptions are supported through arbitrary
copyright-format/copyright-format.xml | 8 +++++---
1 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/copyright-format/copyright-format.xml b/copyright-format/copyright-format.xml
index d6790aa..e558821 100644
@@ -885,10 +885,12 @@ License: MPL-1.1
- Exceptions and clarifications are signaled in plain text, by appending
- <literal>with <varname><replaceable>keywords</replaceable></varname>
+ Exceptions or clarifications are signaled in plain text, by appending
+ <literal>with <varname><replaceable>keyword</replaceable></varname>
exception</literal> to the short name. This document provides a list of
- keywords that refer to the most frequent exceptions.
+ keywords that refer to the most frequent exceptions. In case a license
+ is modified by multiple exceptions or clarifications, a single arbitrary
+ short name must be used.
The GPL <literal>Font</literal> exception refers to the text added to the