From 3aa073296d42b78513d92dcba1c6f0bd6d5f51b8 Mon Sep 17 00:00:00 2001
From: Ulrich Müller <ulm@gentoo.org>
Date: Thu, 9 Jan 2020 11:47:28 +0100
Subject: metadata.dtd: Fix maintainer element.
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

According to GLEP 68, the "maintainer" element is ambiguous:

At top level, it contains in any order:
- exactly one "email" element,
- at most one "name" element,
- zero or more "description" elements.

As subelement of "upstream", it contains in any order:
- exactly one "name" element,
- at most one "email" element.

Since DTD syntax lacks expressiveness, the best we can do (while
keeping things reasonably short) is "(email|name|description)+".

Signed-off-by: Ulrich Müller <ulm@gentoo.org>
Signed-off-by: Michał Górny <mgorny@gentoo.org>
---
 metadata.dtd | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/metadata.dtd b/metadata.dtd
index cb38299..d02c5ac 100644
--- a/metadata.dtd
+++ b/metadata.dtd
@@ -7,7 +7,7 @@
 <!ATTLIST pkgmetadata pkgname CDATA "">
 
   <!-- One tag for each maintainer of a package, multiple allowed-->
-  <!ELEMENT maintainer ( email, (description| name)* )>
+  <!ELEMENT maintainer (email|name|description)+>
   <!-- type attribute determines whether the maintainer is a person or a project.
     Unknown is added to handle <maintainer/>s in <upstream/>s. Using it (or no
     explicit type) for Gentoo maintainers is prohibited. -->
-- 
cgit v1.2.3-65-gdbad