On Dec 14, 2007, at 8:42 AM, Ralf S. Engelschall wrote:

> On Fri, Dec 14, 2007, Jeff Johnson wrote:
>
>> On Dec 14, 2007, at 8:25 AM, Jeff Johnson wrote:
>>
>>> Nice!
>>
>> ... but I'd like to see it go through mireFoo() eventually.
>
> Even better! Please feel free to improve it, Jeff.
>
> I just wanted to be able to give users a "controlled" way of using  
> their
> wished "arbitrary" tags, because I multiple times got a request that
> someone wanted to include custom/local information into a RPM  
> through a
> custom tag but I really always want to be able to clearly identify  
> those
> tags and clearly distinguish them from the official ones. So, a  
> flexible
> but still restricting wildcard based match came to my mind...
>

Just remember that XARv2 is gonna need attributes/properties
written in XML. Whatever permissive (but controlled) configuration
hackery will eventually need to plant a string, not a pattern, into
XML.

ATM, %_arbitrary_tags (and %_dbi_config) are the only place that
the strings are known to rpm. Adding patterns will force some
clunky generic syntax like "Tag_0x12345678" for naming.

There's also the whole issue of encodings for arbitrary tag names that
needs fussing about. We got at least a year to figger what needs  
doing ;-)

73 de Jeff