[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [Debian Perl Group Policy] Proposal for the debian/copyright handling: Should follow copyright-format 1.0

Hi Charles, hi all

On Wed, Jul 11, 2012 at 01:57:57AM +0900, Charles Plessy wrote:
> Le Mon, Jul 09, 2012 at 05:42:23AM +0200, Salvatore Bonaccorso a écrit :
> > 
> > We (Gregor and I) talked during DebCamp with David Prévot if there is
> > a easy way from www team to have a URL pointing to the latest
> > copyright-format released. What we want to say is simply that in the
> > Debian Perl Group every package *should* follow latest released
> > copyright-format.
> Hi Salvatore.
> How about http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightformat ?
> Since the Policy and the specification for the machine-readable format are
> released in the same binary package, it is very likely that this URL will
> always lead to the latest version of the specification.

Okay, sorry I did not came back to this earlier. How about attached
change for the policy?

From 0cb0eb3896c09f39a10d809123a9f6f1ad0d09a2 Mon Sep 17 00:00:00 2001
From: Salvatore Bonaccorso <carnil@debian.org>
Date: Sat, 29 Sep 2012 13:03:08 +0200
Subject: [PATCH] Improve reference to most recent version for

Refer to Debian policy's section about copyright-format in [1].

 [1] http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightformat
 policy.pod |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/policy.pod b/policy.pod
index 2786065..f8f6053 100644
--- a/policy.pod
+++ b/policy.pod
@@ -177,8 +177,8 @@ copyright-format 1.0 or newer. copyright-format 1.0 as released together with
 Debian policy 3.9.3 is documented at
-All released copyright-format specifications can be found under
+The most recent copyright-format specification is referenced in Debian policy
+under L<http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightformat>.
 =head1 debian/watch handling

Attachment: signature.asc
Description: Digital signature

Reply to: