public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Göktürk Yüksek" <gokturk@binghamton.edu>
To: gentoo-portage-dev@lists.gentoo.org
Subject: [gentoo-portage-dev] [PATCH 2/3] xml-test/singularity: tests for at-most-one element violations
Date: Sat,  7 May 2016 17:22:39 -0400	[thread overview]
Message-ID: <1462656160-13578-2-git-send-email-gokturk@binghamton.edu> (raw)
In-Reply-To: <1462656160-13578-1-git-send-email-gokturk@binghamton.edu>

Signed-off-by: Göktürk Yüksek <gokturk@binghamton.edu>
---
 xml-test/singularity/metadata.xml           | 43 +++++++++++++++++++++++++++++
 xml-test/singularity/singularity-0.1.ebuild | 11 ++++++++
 2 files changed, 54 insertions(+)
 create mode 100644 xml-test/singularity/metadata.xml
 create mode 100644 xml-test/singularity/singularity-0.1.ebuild

diff --git a/xml-test/singularity/metadata.xml b/xml-test/singularity/metadata.xml
new file mode 100644
index 0000000..640acf6
--- /dev/null
+++ b/xml-test/singularity/metadata.xml
@@ -0,0 +1,43 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
+<pkgmetadata>
+  <longdescription>
+    Tests for elements with at most one occurrence.
+
+    Singularity doesn't check for uniqueness. We are only interested
+    in elements that can't appear more than once.
+
+    The tests are conservative: if we check &lt;email&gt; element
+    singularity in downstream maintainer, we do not check it again
+    in upstream maintainer.
+  </longdescription>
+  <maintainer type='person'>
+    <email>gen-b0rk@gentoo.org</email>
+    <!-- multiple <email> elements are not allowed -->
+    <email>at-most-one-violation@gentoo.org</email>
+  </maintainer>
+  <slots>
+    <subslots>Match SONAME of libsingularity.so</subslots>
+    <!-- multiple <subslots> elements are not allowed -->
+    <subslots>at-most-one violation</subslots>
+  </slots>
+  <upstream>
+    <maintainer>
+      <name>Gen B0rk</name>
+      <!-- multiple <name> elements are not allowed -->
+      <name>at-most-one violation</name>
+    </maintainer>
+    <changelog>https://gitweb.gentoo.org/repo/proj/gen-b0rk.git/</changelog>
+    <!-- multiple <changelog> elements are not allowed -->
+    <changelog>https://gentoo.org/at-most-one-violation.html</changelog>
+    <bugs-to>http://www.example.com/issues.html</bugs-to>
+    <!-- multiple <bugs-to> elements are not allowed -->
+    <bugs-to>https://gentoo.org/at-most-one-violation</bugs-to>
+  </upstream>
+  <!-- multiple <upstream> elements are not allowed -->
+  <upstream>
+    <maintainer>
+      <name>Gen B0rk</name>
+    </maintainer>
+  </upstream>
+</pkgmetadata>
diff --git a/xml-test/singularity/singularity-0.1.ebuild b/xml-test/singularity/singularity-0.1.ebuild
new file mode 100644
index 0000000..6683aad
--- /dev/null
+++ b/xml-test/singularity/singularity-0.1.ebuild
@@ -0,0 +1,11 @@
+# Copyright 1999-2016 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+# $Id$
+
+EAPI=6
+
+DESCRIPTION="Tests for element singularity"
+HOMEPAGE="https://wiki.gentoo.org/wiki/GLEP:68"
+LICENSE="HPND"
+SLOT="0"
+KEYWORDS="~amd64"
-- 
2.7.3



  reply	other threads:[~2016-05-07 21:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-07 21:22 [gentoo-portage-dev] [PATCH 1/3] xml-text/valid: add a second description to downstream maintainer Göktürk Yüksek
2016-05-07 21:22 ` Göktürk Yüksek [this message]
2016-05-07 21:22 ` [gentoo-portage-dev] [PATCH 3/3] xml-test/uniqueness: tests for unique (element,attribute,value) combinations Göktürk Yüksek

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=1462656160-13578-2-git-send-email-gokturk@binghamton.edu \
    --to=gokturk@binghamton.edu \
    --cc=gentoo-portage-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