On Fri, 04 Mar 2005 23:32:46 +0200, Panu Matilainen <pmatilai@xxxxxxxxx> wrote:
> Scripts and triggers aren't part of the current repodata info but
> *could* added to the "other" stuff along with changelogs where they wont
> slow down typical depsolving activities.
Well when I run across a need to check a trigger related report from
someone in -test-list... say like in fc4t3... expect me to scream and
stomp my feet about it.
The scipts check..sadly..i seem to run across more frequently as I
poke around. I'll probably stomp around about getting access to the
scripts in the 'other' repodata a fair bit as i run into 'i wish i
could check this' situations. And im pretty sure I've already had to
poke into the scripts of some core updates..where even the ondisk core
rpmdb didn't help, but where the repodata for the scripts would have.
> [pmatilai@chip repoquery]$ ./repoquery.py -a --qf "%{name} %{summary}" |
Do you have a full summary of avialable tags that i can use in
-repoquery's --qf?
rpm --querytags lists a lot of them.. and I'd like to have a somewhat
accurate list of what repoquery understands out of that longer list
that rpm knows about. I just don't want to have to guess at the
overlap.
> The leafnode thing is a bit different, but what you're asking for is
> already possible with the prototype/in-progress repoquery: the first is
> direct dependencies on "openssl" package, the second is openssl and
> everything it provides against all configured repositories:
>
> [pmatilai@chip repoquery]$ ./repoquery.py --whatrequires openssl|wc -l
> 21
> [pmatilai@chip repoquery]$ ./repoquery.py --whatrequires --resolve
> openssl|wc -l
> 157
that --resolve switch seems to fill the role if i understand it right.
-jef
