Generating comps.xml
 

Hello,
I've found this quite old document explaining the comps.xml structure:
http://rhlinux.redhat.com/anaconda/comps.html

It mentions the getfullcomps.py script to generate the package sections
of comps.xml. My comps-extras package contains only images and no helper
scripts.


Is comps.xml produced manually nowadays? Is there any tool to automate
comps.xml generation? If not is anybody interested in implementing such
a tool? Is there a need for one?


Thanks,
Alexander.

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

Generating comps.xml
 

As far I know, a tool by name revisor should do what you are suggesting as well as some more things. But, revisor reads from an existing comps file and writes it out into another as per user's selection. It doesnot give support for addiing/modifying/deleting categories and groups in the GUI. Myself and one of my friends are interested in precisely the same. We are modifying revisor's python scripts for doing the same.

With Regards,
Prasad H. L.

----- Original Message ----
From: Alexander Todorov <atodorov@redhat.com>
To: Discussion of Development and Customization of the Red Hat Linux Installer <anaconda-devel-list@redhat.com>
Sent: Thursday, November 22, 2007 3:53:41 PM
Subject: Generating comps.xml


Hello,
I've found this quite old document explaining the comps.xml structure:
http://rhlinux.redhat.com/anaconda/comps.html

It mentions the getfullcomps.py script to generate the package sections

of comps.xml. My comps-extras package contains only images and no
helper
scripts.

Is comps.xml produced manually nowadays? Is there any tool to automate
comps.xml generation? If not is anybody interested in implementing such

a tool? Is there a need for one?

Thanks,
Alexander.

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list





__________________________________________________ __________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

Generating comps.xml
 

Prasad H.L. wrote:

As far I know, a tool by name revisor should do what you are suggesting as well as some more things. But, revisor reads from an existing comps file and writes it out into another as per user's selection. It doesnot give support for addiing/modifying/deleting categories and groups in the GUI. Myself and one of my friends are interested in precisely the same. We are modifying revisor's python scripts for doing the same.


Yes, I'm aware of Revisor and what it does.
Please see here:
http://lists.fedoraunity.org/pipermail/revisor-users/2007-November/000518.html

What I am ultimately looking for is a tool that will generate comps.xml
skeleton based on directory containing RPM packages. AFAIK no such tool
exists.


As it's been long time since comps.xml exist and no automation tool is
used I wonder why. Is automation bringing a lot more issues that take
more time to solve that hand crafting the comps or simply nobody was
interested in writing a tool?


Greetings,
Alexander.

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

Generating comps.xml
 

On Thu, Nov 22, 2007 at 11:44:32AM +0100, Alexander Todorov wrote:

> What I am ultimately looking for is a tool that will generate comps.xml
> skeleton based on directory containing RPM packages. AFAIK no such tool
> exists.

But what groups and categories you want to idenify, and what packages
you want to be included in a group as default, mandatory, and optional
can not be automated without extra information.

--
-- Jos Vos <jos@xos.nl>
-- X/OS Experts in Open Systems BV | Phone: +31 20 6938364
-- Amsterdam, The Netherlands | Fax: +31 20 6948204

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

Generating comps.xml
 

Jos Vos wrote:

On Thu, Nov 22, 2007 at 11:44:32AM +0100, Alexander Todorov wrote:

What I am ultimately looking for is a tool that will generate comps.xml
skeleton based on directory containing RPM packages. AFAIK no such tool
exists.


But what groups and categories you want to idenify, and what packages
you want to be included in a group as default, mandatory, and optional
can not be automated without extra information.



Group information can be extracted from the RPM package:
e.g. Group : System Environment/Base may result in
system-environment group with base subgroup or something like that.
This group includes the packages that are tagged with that group name in
the .spec file.


You are right that default, mandatory and optional is hardly automated.
For that one needs a criteria of some kind (that is probably missing in
the RPM file).


Still that can be useful for 3rd party/private repositories especially
when remixing Fedora. As of now I think there is no way to get 3rd party
packages visible in Anaconda GUI other than comps.xml or you need a
ks.cfg file to install these packages.


I am not at all sure if auto generation tool will help and that's why I
need more opinions.


Greetings,
Alexander.

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

Generating comps.xml
 

On Thu, Nov 22, 2007 at 12:07:51PM +0100, Alexander Todorov wrote:

> Group information can be extracted from the RPM package:
> e.g. Group : System Environment/Base may result in
> system-environment group with base subgroup or something like that.
> This group includes the packages that are tagged with that group name in
> the .spec file.

This assumes there is a one-to-one mapping between used RPM group names
and comps groups. AFAIK this is currently not the case. It could be
done that way, as the RPM group tag is not used for anything else at this
moment (in the past anaconda used it for showing a tree structure, IIRC).

> You are right that default, mandatory and optional is hardly automated.
> For that one needs a criteria of some kind (that is probably missing in
> the RPM file).

As the RPM group tag is just a string, you could probably even include it
there, like with "Group: base(optional)" or "Group: kde-desktop(mandatory)".

--
-- Jos Vos <jos@xos.nl>
-- X/OS Experts in Open Systems BV | Phone: +31 20 6938364
-- Amsterdam, The Netherlands | Fax: +31 20 6948204

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/anaconda-devel-list