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

[Bernd Hentig]

>> 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.
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?

Regards
Bernd
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bernd.vcf
Type: text/x-vcard
Size: 300 bytes
Desc: not available
Url : http://lists.fedoraunity.org/pipermail/revisor-users/attachments/20071123/87b57206/attachment.vcf