On Mon, Mar 24, 2008 at 4:35 PM, Michael Stahnke <mastahnke(a)gmail.com> wrote:
On Mon, Mar 24, 2008 at 5:34 PM, Michael Stahnke
<mastahnke(a)gmail.com> wrote:
> I probably won't make the meeting.
>
> > RHEL Meta Data
> As I tried to explain in the past, this is difficult, because it's an
> unknown target. Some people want full search capabilities of RHN, and
> we can't easily provide that. For most cases, however, repoquery and
> yum give enough good information.
> The most common use cases I see are:
> * What's the version of package XYZ in RHEL? (Use yum/repoquery)
> * Is package XYZ included in RHEL? (Use yum/repoquery)
> * What are the differences in packages between CentOS and RHEL ? (
>
http://wiki.centos.org/Manuals/ReleaseNotes/CentOS5.1/#head-bcaed48ff6432...)
>
> More obscure cases
> * What package provides lib-XYZ?
> * How do I see the changelog for packages? (Repoquery again)
> * Is package foo included in other Red Hat channel other than base
> RHEL. (This one is a bit harder).
> * What packages are coming up in RHEL version X.Y+1 that will
> obsolete EPEL packages? (again, not a clear way)
>
>
>
>
>
> stahnma
>
Basically, if we could put a really nice front end on repoquery, most
problems would be easily solved. I think some of the issues are not
everyone having an EL box to build upon.
Does the equivalent of the old 'comps' rpm give equivalent information?
And thanks for the update.
--
Stephen J Smoogen. -- CSIRT/Linux System Administrator
How far that little candle throws his beams! So shines a good deed
in a naughty world. = Shakespeare. "The Merchant of Venice"