Centos wrote:
Not sure if I understand want you mean, but...
You can do a nobase install, list all installed packages (rpm -qa), and
save this to a file. Then install the base, en list all installed
packages again. Export again to a file en diff those two files...
Ah, I should've thought of
Johnny Hughes wrote:
Probably the easiest way to do what you want is to look at the comps.xml
file directly.
Awesome! A bit hard to read, but it was exactly what I was
looking for. It actually has the "core" group and the "base"
group separate!
Thanks Johnny.
johnn
Not sure if I understand want you mean, but...
You can do a nobase install, list all installed packages (rpm -qa), and
save this to a file. Then install the base, en list all installed
packages again. Export again to a file en diff those two files...
Hope this helps.
Cheers,
Bart
Johnny Hu
Johnn Tan wrote:
> Is there a way to list the packages that are in a "base" install, but
> that are not in a "nobase" (core) install?
>
> I did a nobase install, then ran "yum groupinstall Base", but this just
> lists everything in base, including the core packages.
>
> Mainly, I'm just looking t
Is there a way to list the packages that are in a "base"
install, but that are not in a "nobase" (core) install?
I did a nobase install, then ran "yum groupinstall Base",
but this just lists everything in base, including the core
packages.
Mainly, I'm just looking to audit the packages, and
5 matches
Mail list logo