On Thu, 2006-02-16 at 13:17 +0100, Chitlesh GOORAH wrote:
>hmm I dont think It has because with
>
>
Your repodata error is due to a bad URL, device is to be replaced with
the device node, e.g. cdrom://hdd://
however, this isn't neccessary now. All you need to do is use
/path/to/dvdrom
I'll run this down really quick, without diving into the codebase and
posting it, as users can check it out of CVS if they wish.
Kadischi does simple checks to make sure your repository path exists,
along with it's required directories, which
are Fedora/{base,RPMS}, and makes certain your destination file is ok.
Kadischi will spawn Anaconda passing the method, and rootpath along with
any other options you give
which soon should be passed along to Anaconda(This is in the TODO in
Kadischi/Schedule).
If the method isn't an FTP or HTTP repository source, it formats it
nicely for Anaconda as nfs://path/to/repo
Optical and local media, HTTP, and FTP repositories can be used. This
pretty much covers alot of standard methods for repository source.
Anaconda of course does it's required checks and takes the neccessary
steps to complete the installation.
Kadischi then does the required steps to make an ISO.
That is the basis of Kadischi's operation.
Kadischi is essentially going to become more integrated with Anaconda.
I don't think the presentation of patching and etc etc is neccessary
either and I'll tell yuo why.
What is in CVS now, is absolutely subject to change.
Kadischi is going to have alot of work done to/with it to get it usable,
as Jeremy stated, not needing to know anything
but how to do basic installation procedures. There isn't a need for
presentations on patches.
What I think would benefit the project if a presentation is made, would
be to present:
1) The running of Kadischi
2) The product of Kadischi
J. Hartline