[Fedora-livecd-list] Status of kadischi ?

[J. Hartline]

It is sort of funny you ask that, some RFEs have been getting filed on 
alot of these utilities, anaconda and yum alike.
They are excellent tools, I mean they work.
I suppose you could contact Jeremy Katz on anaconda-deve-list and ask him.

As far as comps is concerned, it is fairly easy.
Here is an example scenario..
You have KDE and Gnome. You can't install anything on that LiveCD after 
it has been spun.
You want Fluxbox? comps.xml is where you need to be.
 From start to end, you'll need to put fluxbox and all of it's deps into 
your repository.
Run pkgorder and genhdlist to reflect these changes.
Open up comps.xml (I'll leave alot of this research for you to do on 
your own, you could possibly contribute to the wiki?)
This sounds like a KadischiFAQ to me.

It is going to be like this pretty much: <group>
                                                                          
<id>GroupID</id>
                                                                          
<name language>Name</name>
                                                                          
<description>Small descriptional text</description>
For groups, you will have settings for <default>true</default> or false, 
depending on whether it should install, by default.
You will likewise have: <uservisible> which is just what it means. True 
or false.
<packagelist>
      <packagereq type="mandatory">foo</packagereq>
      <packagereq type="mandatory">bar</packagereq>
       <packagereq type="optional">foo-bar</packagereq>
    </packagelist>
  </group> (End of that Group.)

And thats it for a Group. Remember what your GroupID was you had set 
earlier.
Lets bounce to the bottom of comps.xml.
We have: <category> and <subcategory> we also have <grouplist> and 
<groupreq>.
You will use your <id>\\//</id> with these.
They go in a simple descending order. Groups, Categories with 
subcategories and Grouplists and GroupRequirements
and finally GroupHierarchies, such as Desktop, Workstation, Server, 
Everything and Minimal.

I'll leave the brainstorming to you. Don't forget to run pkgorder and 
genhdlist if you plan you use anything except Fedora Core
provided stock packages. If you put updates in your repositories, run 
these tools also. Things can and will change in packages.
This should help you get an idea of how Anaconda will devide things up.

J. Hartline

Ok. I hope this helps a bit.
Chris Negus wrote:

>Is there any documentation available on the anaconda-runtime utilities?
>Is vi the tool for modifying comps.xml? If someone can help me figure
>out how to do it, I'd be glad to write up a procedure for incorporating
>a custom set of packages into the build of a Fedora live CD. Thanks!
>
>-- Chris Negus
>
>
>  
>