On Mon, Mar 24, 2008 at 5:34 PM, Michael Stahnke <[EMAIL PROTECTED]> 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-bcaed48ff64328cc23cbef681289c5d8ae7efa05) > > 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. _______________________________________________ epel-devel-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/epel-devel-list
