[Revisor-users] Some questions on comps.xml and kcikstart file

[Jeroen van Meeuwen]

>
>>> Here is a quick and simple idea. It probably needs some bug fixing:
>>> 1) During RPM download phase generate a list of available packages.
>>> This
>>> is what will end up on the final media and ideally dependencies are
>>> satisfies (unless something goes wrong)
>>>
>>> 2) Merge comps.xml files found in all repositories as it is now.
>>> 3) For each <group> tag inspect the <packagelist> and <packagereq>
>>> tags.
>>> If the listed package is not in the list of downloaded packages then
>>> remove it from XML.
>>>
> What will happen to packages in a repo that are not listed in any
> comps.xml?
> I.e. the packages from the former "extras" repo do not have an entry in
> any comps.xml AFAIK,
> so they will usually not be selectable in any category.

Note that these packages may very well just provide some library and isn't
something you would want to select, rather then just pulled in. You could
always provide an empty repository with your additions to comps -if you
feel like it. You could also provide a kickstart with interactive
installation, but preselecting (some) packages.

> But all RPMs come with their own - internal - field "Group", shouldn't
> this be used instead?
> BTW, what is the normal purpose of the RPM "Group" field, if it has no
> relation to the comps.xml?
>

That's right. The RPM Group: header, afaik, isn't used by anything -e.g.
not yum, and isn't related to comps in any way.

Kind regards,

Jeroen van Meeuwen
-kanarip
> Regards
> Bernd
> _______________________________________________
> Revisor-users mailing list
> Revisor-users at fedoraunity.org
> http://lists.fedoraunity.org/mailman/listinfo/revisor-users
>