From: "Justin <jlec>" <jlec@gentoo.org>
To: Ulrich Mueller <ulm@gentoo.org>, gentoo-dev@lists.gentoo.org
Cc: Davide Pesavento <pesa@gentoo.org>, qa@gentoo.org, cardoe@gentoo.org
Subject: Re: [gentoo-dev] XML Schema files for metadata.xml, projects.xml and repositories.xml, for review and testing
Date: Sun, 6 Mar 2016 20:22:18 +0000 [thread overview]
Message-ID: <56DC917A.9010402@gentoo.org> (raw)
In-Reply-To: <22236.34017.614512.823764@a1i15.kph.uni-mainz.de>
On 06/03/16 19:28, Ulrich Mueller wrote:
>>>>>> On Sun, 6 Mar 2016, Michał Górny wrote:
>
>> On Sun, 6 Mar 2016 19:26:15 +0100
>> Davide Pesavento <pesa@gentoo.org> wrote:
>
>>> So I guess we could use the following form when SLOTs are needed:
>>> <pkg>media-libs/gstreamer</pkg>:1.0
>>> ?
>
>> Prolly.
>
>> Just to be clear, I have no clue what the original use of <pkg/>
>> was and what the final outcome of this will be. This thread was
>> established mostly in order to determine that. I'd wait for ulm to
>> turn up and have some suggestions ;-).
>
> :)
>
> No idea what the original purpose was, but <pkg> and <cat> are
> specified in GLEP 56 [1]:
>
> - Each <flag> XML tag allows 0 or more nested <pkg> XML tags whose
> character data is a valid CP or CPV as defined by the Gentoo
> Development Manual - Ebuild File Format [2].
Michał, your current syntax breaks with multiple pkg
(<pkg>sci-libs/metis</pkg> or <pkg>sci-libs/parmetis</pkg>)
results in
metadata.xml:21: element pkg: Schemas validity error : Element 'pkg':
[facet 'pattern'] The value '' is not accepted by the pattern
'[A-Za-z0-9_][A-Za-z0-9+_.-]*/[A-Za-z0-9_][A-Za-z0-9+_-]*'.
metadata.xml:21: element pkg: Schemas validity error : Element 'pkg': ''
is not a valid value of the atomic type 'pkgType'.
metadata.xml:24: element pkg: Schemas validity error : Element 'pkg':
[facet 'pattern'] The value '' is not accepted by the pattern
'[A-Za-z0-9_][A-Za-z0-9+_.-]*/[A-Za-z0-9_][A-Za-z0-9+_-]*'.
metadata.xml:24: element pkg: Schemas validity error : Element 'pkg': ''
is not a valid value of the atomic type 'pkgType'.
Justin
next prev parent reply other threads:[~2016-03-06 20:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-06 11:01 [gentoo-dev] XML Schema files for metadata.xml, projects.xml and repositories.xml, for review and testing Michał Górny
2016-03-06 11:04 ` Michał Górny
2016-03-06 11:27 ` Sergei Trofimovich
2016-03-06 12:24 ` Davide Pesavento
2016-03-06 18:12 ` Justin <jlec>
2016-03-06 18:18 ` Michał Górny
2016-03-06 18:26 ` Davide Pesavento
2016-03-06 18:31 ` Michał Górny
2016-03-06 19:28 ` Ulrich Mueller
2016-03-06 19:35 ` Michał Górny
2016-03-06 20:22 ` Justin <jlec> [this message]
2016-03-06 20:49 ` Michał Górny
2016-03-06 21:34 ` Justin <jlec>
2016-03-06 18:31 ` Justin <jlec>
2016-03-06 18:25 ` Kent Fredric
-- strict thread matches above, loose matches on Subject: below --
2016-03-06 9:43 Michał Górny
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=56DC917A.9010402@gentoo.org \
--to=jlec@gentoo.org \
--cc=cardoe@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=pesa@gentoo.org \
--cc=qa@gentoo.org \
--cc=ulm@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