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 3/3] xml-test/uniqueness: tests for unique (element,attribute,value) combinations
Date: Sat,  7 May 2016 17:22:40 -0400	[thread overview]
Message-ID: <1462656160-13578-3-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/uniqueness/metadata.xml          | 33 +++++++++++++++++++++++++++++++
 xml-test/uniqueness/uniqueness-0.1.ebuild | 12 +++++++++++
 2 files changed, 45 insertions(+)
 create mode 100644 xml-test/uniqueness/metadata.xml
 create mode 100644 xml-test/uniqueness/uniqueness-0.1.ebuild

diff --git a/xml-test/uniqueness/metadata.xml b/xml-test/uniqueness/metadata.xml
new file mode 100644
index 0000000..84b3a1b
--- /dev/null
+++ b/xml-test/uniqueness/metadata.xml
@@ -0,0 +1,33 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
+<pkgmetadata>
+  <longdescription>
+    Tests for the uniqueness of elements.
+
+    Uniqueness focuses on element, attribute, value combinations
+    which must not repeat.
+
+    The tests are conservative: i.e. if we check the
+    (longdescription, lang, restrict) combination, we do not check
+    (slots,lang, restrict).
+  </longdescription>
+  <!-- non-unique (longdescription, lang, restrict) combination -->
+  <longdescription lang='en'>uniqueness violation</longdescription>
+  <maintainer type='person'>
+    <email>gen-b0rk@gentoo.org</email>
+  </maintainer>
+  <maintainer type='project'>
+    <!-- non-unique (maintainer, email, restrict) combination -->
+    <email>gen-b0rk@gentoo.org</email>
+  </maintainer>
+  <slots>
+    <slot name="0">Match the SONAME of libuniqueness.so</slot>
+    <!-- non-unique (slot, name, restrict) combination -->
+    <slot name="0">uniqueness violation</slot>
+  </slots>
+  <use>
+    <flag name="foo">Enable feature foo</flag>
+    <!-- non-unique (flag, name, restrict) combination -->
+    <flag name="foo">uniqueness violation</flag>
+  </use>
+</pkgmetadata>
diff --git a/xml-test/uniqueness/uniqueness-0.1.ebuild b/xml-test/uniqueness/uniqueness-0.1.ebuild
new file mode 100644
index 0000000..03c3fa7
--- /dev/null
+++ b/xml-test/uniqueness/uniqueness-0.1.ebuild
@@ -0,0 +1,12 @@
+# Copyright 1999-2016 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+# $Id$
+
+EAPI=6
+
+DESCRIPTION="Tests for (element, attribute, value) uniqueness"
+HOMEPAGE="https://wiki.gentoo.org/wiki/GLEP:68"
+LICENSE="HPND"
+SLOT="0"
+KEYWORDS="~amd64"
+IUSE="foo"
-- 
2.7.3



      parent 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 ` [gentoo-portage-dev] [PATCH 2/3] xml-test/singularity: tests for at-most-one element violations Göktürk Yüksek
2016-05-07 21:22 ` Göktürk Yüksek [this message]

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-3-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