-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Michał Górny: > On Sat, 14 May 2016 20:57:48 -0400 Göktürk Yüksek > <gokt...@binghamton.edu> wrote: > >> @@ -244,12 +221,7 @@ optional: without this attribute must also >> exist. That tag without the restrict attribute will serve as the >> default. The format of the restrict attribute is that of the >> DEPEND flag, except that "<" and - ">" need to be >> specified by &lt; and &gt;.<br /> - <br /> - For >> example, in the <c>sys-libs/db</c> package, - >> <c>restrict="&gt;=sys-libs/db-3.2.9-r5"</c> on the - >> <brite>maintainer</brite> tag shows that I'm currently >> maintaining all - versions greater then 3.2.9-r5. + ">" >> need to be specified by "&lt;" and "&gt;". </ti> </tr> >> <tr> > > I'm sorry for coming late to the party but could you mention that > it must be an EAPI 0 package dependency? There were more than a > few packages where people put slot- or USE-dependencies there. >
The purpose of this change was to remove the example inside the table since I've added a complete example with restrict under the metadata examples section. PATCH 3/4 accomplishes what you ask: + the restrict attribute serves as the default. The format of the + restrict attribute is that of a EAPI=0 package dependency + specification. Due to the limitations of XML, the "<" and -----BEGIN PGP SIGNATURE----- iQEcBAEBCgAGBQJXOS8RAAoJEIT4AuXAiM4z21sH+wWVlhYAZpGTIaBJydWWnynI zuF1CmHxb4dlLh9zbwMcMuRavbxYbKsI3P0D2p4h1kNI6a9jZzAAvHF99eTC6o54 +PjwgxroxtTHKrp147Jmubrj+u70EWvj2JGxIprRkS5A0ZW+zE24n37IA/8AtwEL XV24dB1HSs98WkfJbnhYmS6nxyQHz0fiFRM4o1syxtHyu9bS1zXE+fEevqeTOo4i PlqJCgyepvyPdcYeDHVOz7b9MqXy19+GTPFxHzfoHMBWB4/X/6umYE+1n9CRIjeX THhiCZ/6uXVvXJgUcaoLlWE984wbgEzt9j4zp2CJqG0FgyndtCuW9QZrY8gWW4I= =kmMC -----END PGP SIGNATURE-----
