Re: Bug#758124: Documenting the Testsuite field in the Policy.
On Tue, Aug 19, 2014 at 07:35:22PM -0300, Antonio Terceiro wrote: Anybody Developer who thinks that 1) the Policy is useful and 2) the Testsuite field is useful, can participate. What is needed is to read the text below, verify that it reflects the facts, and if yes, send an email containing something like “seconded”. IMO the fact that close to 600 packages are already using the field shows quite some support for it to be documented. :) I somehow was guided by this idea when I was raising my hand the first time. And yes, I agree that we should document what we are using. + headingttTestsuite/tt/heading + + p + Simple field containing a comma-separated list of values allowing + test execution environments to discover packages which provide + tests. Currently, the only defined value is ttautopkgtest/tt. + /p + + p + This field is automatically added to Debian source control files by + prgndpkg/prgnfootnotefrom version 1.17.11./footnote when + a filedebian/tests/control/file file is present in the source + package. This field may also be used in source package control + files if needed in other situations. + /p Looks good to me. Seconded, FWIW. I wonder whether the second paragraph implies something like: Since the field is automatically added there is no reason to specify it explicitly any more. I think this policy change is even implemented in lintian since I think to remember that lintian stopped warning about the missing testsuite field (if I remember correctly without checking). Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140820113832.go15...@an3as.eu
Re: Bug#758124: Documenting the Testsuite field in the Policy.
On Wed, Aug 20, 2014 at 01:38:32PM +0200, Andreas Tille wrote: On Tue, Aug 19, 2014 at 07:35:22PM -0300, Antonio Terceiro wrote: Anybody Developer who thinks that 1) the Policy is useful and 2) the Testsuite field is useful, can participate. What is needed is to read the text below, verify that it reflects the facts, and if yes, send an email containing something like “seconded”. IMO the fact that close to 600 packages are already using the field shows quite some support for it to be documented. :) I somehow was guided by this idea when I was raising my hand the first time. And yes, I agree that we should document what we are using. + headingttTestsuite/tt/heading + + p + Simple field containing a comma-separated list of values allowing + test execution environments to discover packages which provide + tests. Currently, the only defined value is ttautopkgtest/tt. + /p + + p + This field is automatically added to Debian source control files by + prgndpkg/prgnfootnotefrom version 1.17.11./footnote when + a filedebian/tests/control/file file is present in the source + package. This field may also be used in source package control + files if needed in other situations. + /p Looks good to me. Seconded, FWIW. I wonder whether the second paragraph implies something like: Since the field is automatically added there is no reason to specify it explicitly any more. I think this policy change is even implemented in lintian since I think to remember that lintian stopped warning about the missing testsuite field (if I remember correctly without checking). There are cases when you want to add it explicitly, e.g. when someone comes up with a new possible value for it that is not automatically added yet. Testsuite: mynewthing or even Testsuite: autopkgtest, mynewthing So maybe we could review the text like this: headingttTestsuite/tt/heading p Simple field containing a comma-separated list of values allowing test execution environments to discover packages which provide tests. Currently, the only defined value is ttautopkgtest/tt. /p p prgndpkg-source/prgnfootnotefrom prgndpkg-dev/prgn version 1.17.11./footnote will automatically add this field to Debian source control files with the value ttautopkgtest/tt if a filedebian/tests/control/file file is present in the source package. This field may also be used in source package control files if needed in other situations, for example to declare other test suite handlers that are not yet automatically detected by dpkg. /p -- Antonio Terceiro terce...@debian.org signature.asc Description: Digital signature
Re: Bug#758124: Documenting the Testsuite field in the Policy.
Hi Charles, On Tue, Aug 19, 2014 at 07:44:19AM +0900, Charles Plessy wrote: Le Thu, Aug 14, 2014 at 09:36:50PM +0900, Charles Plessy a écrit : Package: debian-policy Version: 3.9.5 Severity: wishlist Hi Guillem and everybody, thanks for adding direct support for the Testsuite field in Dpkg. Here is a patch to update the Policy accordingly. Do you have comments ? Anybody wanting to see the Testsuite field documented in the Policy, please raise your hand ! Raise my hand ... but for what purpose? Is policy a matter of voting about it? BTW, if I remember correctly recent dpkg will add the field automatically so perhaps the documentation for the user might become less important (or am I wrong here)? Kind regards Andreas. Have a nice day, -- Charles diff --git a/policy.sgml b/policy.sgml index 6eac491..a8b27e2 100644 --- a/policy.sgml +++ b/policy.sgml @@ -2666,6 +2666,7 @@ Package: libc6 itemqref id=f-Standards-VersionttStandards-Version/tt/qref (recommended)/item itemqref id=f-HomepagettHomepage/tt/qref/item itemqref id=f-VCS-fieldsttVcs-Browser/tt, ttVcs-Git/tt, et al./qref/item + itemqref id=f-TestsuitettTestsuite/tt/qref/item /list /p @@ -2761,6 +2762,7 @@ Package: libc6 itemqref id=f-UploadersttUploaders/tt/qref/item itemqref id=f-HomepagettHomepage/tt/qref/item itemqref id=f-VCS-fieldsttVcs-Browser/tt, ttVcs-Git/tt, et al./qref/item + itemqref id=f-TestsuitettTestsuite/tt/qref/item itemqref id=f-DgitttDgit/tt/qref/item itemqref id=f-Standards-VersionttStandards-Version/tt/qref (recommended)/item itemqref id=sourcebinarydepsttBuild-Depends/tt et al/qref/item @@ -3863,6 +3865,24 @@ Checksums-Sha256: further details. /p /sect1 + + sect1 id=f-Testsuite + headingttTestsuite/tt/heading + + p + Simple field containing a comma-separated list of values allowing + test execution environments to discover packages which provide + tests. Currently, the only defined value is ttautopkgtest/tt. + /p + + p + This field is automatically added to Debian source control files by + prgndpkg/prgnfootnotefrom version 1.17.11./footnote when + a filedebian/tests/control/file file is present in the source + package. This field may also be used in source package control + files if needed in other situations. + /p + /sect1 /sect sect -- 2.0.1 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140818224419.GA7618@aqwa.igloo -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140819134826.ga25...@an3as.eu
Re: Bug#758124: Documenting the Testsuite field in the Policy.
Le Thu, Aug 14, 2014 at 09:36:50PM +0900, Charles Plessy a écrit : Here is a patch to update the Policy accordingly. Do you have comments ? On Tue, Aug 19, 2014 at 07:44:19AM +0900, Charles Plessy wrote: Anybody wanting to see the Testsuite field documented in the Policy, please raise your hand ! Le Tue, Aug 19, 2014 at 03:48:26PM +0200, Andreas Tille a écrit : Raise my hand ... but for what purpose? Is policy a matter of voting about it? BTW, if I remember correctly recent dpkg will add the field automatically so perhaps the documentation for the user might become less important (or am I wrong here)? Hi Andreas, changes to the Policy work by consensus, so if out of ~1,000 developers there is not a single one who supports a proposed change, then nothing will happen, because a wall of silence is a sign of reprobation. This is actually very efficient to make nothing happen. As to whether document or not this field, my personal opinion is that Policy's chapter 5, which documents most fields, should be comprehensive. But perhaps I over-value the Policy ? Still, I think that it is one asset that Debian has and other distributions do not. But yes, we can do without if we do not have the manpower to prevent it from bitrotting. Anybody Developer who thinks that 1) the Policy is useful and 2) the Testsuite field is useful, can participate. What is needed is to read the text below, verify that it reflects the facts, and if yes, send an email containing something like “seconded”. + headingttTestsuite/tt/heading + + p + Simple field containing a comma-separated list of values allowing + test execution environments to discover packages which provide + tests. Currently, the only defined value is ttautopkgtest/tt. + /p + + p + This field is automatically added to Debian source control files by + prgndpkg/prgnfootnotefrom version 1.17.11./footnote when + a filedebian/tests/control/file file is present in the source + package. This field may also be used in source package control + files if needed in other situations. + /p The whole process for changing the Policy is described in details at the URL below: https://wiki.debian.org/PolicyChangesProcess Have a nice day, Charles -- Charles Plessy Tsurumi, Kanagawa, Japan -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140819213439.ga13...@falafel.plessy.net
Re: Bug#758124: Documenting the Testsuite field in the Policy.
On Wed, Aug 20, 2014 at 06:34:39AM +0900, Charles Plessy wrote: Le Thu, Aug 14, 2014 at 09:36:50PM +0900, Charles Plessy a écrit : Here is a patch to update the Policy accordingly. Do you have comments ? On Tue, Aug 19, 2014 at 07:44:19AM +0900, Charles Plessy wrote: Anybody wanting to see the Testsuite field documented in the Policy, please raise your hand ! Le Tue, Aug 19, 2014 at 03:48:26PM +0200, Andreas Tille a écrit : Raise my hand ... but for what purpose? Is policy a matter of voting about it? BTW, if I remember correctly recent dpkg will add the field automatically so perhaps the documentation for the user might become less important (or am I wrong here)? Hi Andreas, changes to the Policy work by consensus, so if out of ~1,000 developers there is not a single one who supports a proposed change, then nothing will happen, because a wall of silence is a sign of reprobation. This is actually very efficient to make nothing happen. As to whether document or not this field, my personal opinion is that Policy's chapter 5, which documents most fields, should be comprehensive. But perhaps I over-value the Policy ? Still, I think that it is one asset that Debian has and other distributions do not. But yes, we can do without if we do not have the manpower to prevent it from bitrotting. Anybody Developer who thinks that 1) the Policy is useful and 2) the Testsuite field is useful, can participate. What is needed is to read the text below, verify that it reflects the facts, and if yes, send an email containing something like “seconded”. IMO the fact that close to 600 packages are already using the field shows quite some support for it to be documented. :) + headingttTestsuite/tt/heading + + p + Simple field containing a comma-separated list of values allowing + test execution environments to discover packages which provide + tests. Currently, the only defined value is ttautopkgtest/tt. + /p + + p + This field is automatically added to Debian source control files by + prgndpkg/prgnfootnotefrom version 1.17.11./footnote when + a filedebian/tests/control/file file is present in the source + package. This field may also be used in source package control + files if needed in other situations. + /p Looks good to me. Seconded, FWIW. -- Antonio Terceiro terce...@debian.org signature.asc Description: Digital signature
Re: Bug#758124: Documenting the Testsuite field in the Policy.
Le Thu, Aug 14, 2014 at 09:36:50PM +0900, Charles Plessy a écrit : Package: debian-policy Version: 3.9.5 Severity: wishlist Hi Guillem and everybody, thanks for adding direct support for the Testsuite field in Dpkg. Here is a patch to update the Policy accordingly. Do you have comments ? Anybody wanting to see the Testsuite field documented in the Policy, please raise your hand ! Have a nice day, -- Charles diff --git a/policy.sgml b/policy.sgml index 6eac491..a8b27e2 100644 --- a/policy.sgml +++ b/policy.sgml @@ -2666,6 +2666,7 @@ Package: libc6 itemqref id=f-Standards-VersionttStandards-Version/tt/qref (recommended)/item itemqref id=f-HomepagettHomepage/tt/qref/item itemqref id=f-VCS-fieldsttVcs-Browser/tt, ttVcs-Git/tt, et al./qref/item + itemqref id=f-TestsuitettTestsuite/tt/qref/item /list /p @@ -2761,6 +2762,7 @@ Package: libc6 itemqref id=f-UploadersttUploaders/tt/qref/item itemqref id=f-HomepagettHomepage/tt/qref/item itemqref id=f-VCS-fieldsttVcs-Browser/tt, ttVcs-Git/tt, et al./qref/item + itemqref id=f-TestsuitettTestsuite/tt/qref/item itemqref id=f-DgitttDgit/tt/qref/item itemqref id=f-Standards-VersionttStandards-Version/tt/qref (recommended)/item itemqref id=sourcebinarydepsttBuild-Depends/tt et al/qref/item @@ -3863,6 +3865,24 @@ Checksums-Sha256: further details. /p /sect1 + + sect1 id=f-Testsuite + headingttTestsuite/tt/heading + + p + Simple field containing a comma-separated list of values allowing + test execution environments to discover packages which provide + tests. Currently, the only defined value is ttautopkgtest/tt. + /p + + p + This field is automatically added to Debian source control files by + prgndpkg/prgnfootnotefrom version 1.17.11./footnote when + a filedebian/tests/control/file file is present in the source + package. This field may also be used in source package control + files if needed in other situations. + /p + /sect1 /sect sect -- 2.0.1 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140818224419.GA7618@aqwa.igloo
Bug#758124: Documenting the Testsuite field in the Policy.
Package: debian-policy Version: 3.9.5 Severity: wishlist Hi Guillem and everybody, thanks for adding direct support for the Testsuite field in Dpkg. Here is a patch to update the Policy accordingly. Do you have comments ? Have a nice day, -- Charles Plessy Tsurumi, Kanagawa, Japan From b2679f5e6e871c3316625d231ef88e5858d1b57c Mon Sep 17 00:00:00 2001 From: Charles Plessy ple...@debian.org Date: Thu, 14 Aug 2014 21:30:47 +0900 Subject: [PATCH] Document the Testsuite field. --- policy.sgml | 20 1 file changed, 20 insertions(+) diff --git a/policy.sgml b/policy.sgml index 6eac491..a8b27e2 100644 --- a/policy.sgml +++ b/policy.sgml @@ -2666,6 +2666,7 @@ Package: libc6 itemqref id=f-Standards-VersionttStandards-Version/tt/qref (recommended)/item itemqref id=f-HomepagettHomepage/tt/qref/item itemqref id=f-VCS-fieldsttVcs-Browser/tt, ttVcs-Git/tt, et al./qref/item + itemqref id=f-TestsuitettTestsuite/tt/qref/item /list /p @@ -2761,6 +2762,7 @@ Package: libc6 itemqref id=f-UploadersttUploaders/tt/qref/item itemqref id=f-HomepagettHomepage/tt/qref/item itemqref id=f-VCS-fieldsttVcs-Browser/tt, ttVcs-Git/tt, et al./qref/item + itemqref id=f-TestsuitettTestsuite/tt/qref/item itemqref id=f-DgitttDgit/tt/qref/item itemqref id=f-Standards-VersionttStandards-Version/tt/qref (recommended)/item itemqref id=sourcebinarydepsttBuild-Depends/tt et al/qref/item @@ -3863,6 +3865,24 @@ Checksums-Sha256: further details. /p /sect1 + + sect1 id=f-Testsuite + headingttTestsuite/tt/heading + + p + Simple field containing a comma-separated list of values allowing + test execution environments to discover packages which provide + tests. Currently, the only defined value is ttautopkgtest/tt. + /p + + p + This field is automatically added to Debian source control files by + prgndpkg/prgnfootnotefrom version 1.17.11./footnote when + a filedebian/tests/control/file file is present in the source + package. This field may also be used in source package control + files if needed in other situations. + /p + /sect1 /sect sect -- 2.0.1
