[Rpm-metadata] more code and an idea

[Daniel Veillard]

On Fri, Dec 05, 2003 at 02:20:30AM -0500, seth vidal wrote:
> Also,  I was talking to someone from ximian in irc the other day and
> they mentioned a need for versions in the groups/comps file.
> 
> ie:
>  <group>
>    ...
>    <packagereq name='foo'>
>      <version epoch="1" ver="1.1.19" rel="12"/>
>    </packagereq>
>  </group>

  Hum, it's actually a case where I think the extra structure brings nothing
    <packagereq name='foo' epoch="1" ver="1.1.19" rel="12"/>
looks just as good unless you start making complex composition within 
one packagereq ...

> Is that something other people would be interested in? would this work
> out overall?

  Well, well, how far are we from closing the initial goal of providing the
metadata needed for tools like up2date, yum, apt, red-carpet when they build
a package update/lookup transation ? I would feel far more comfortable pushing
for new additional formats once we have done at least the first round of
experiment generating those data, testing with at least a pair of tools and
made the first round of public testing. So what is needed now to make
progress toward that initial goal ?

Daniel

-- 
Daniel Veillard      | Red Hat Network https://rhn.redhat.com/
veillard at redhat.com  | libxml GNOME XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/