Hi, > I guess I'm confused here. Your next point down you want libraries > for rpm. > But you are opposed to it for cpio? I want the libarchive to go there, just not now, since we need to test this first and the cipo code was tested and works. So before replacing any components, I would like to concentrate on the overall design testing than on particular pieces which could be replaced later. > What else is needed beyond unpacking the RPMs? That's probably where > my > misunderstanding is. I'm under the impression that we simply need to > unpack > the RPM, pull out the .ko files, and let modprobe load them so we can > use > those devices during installation. Is there more? We only want to explode packages which profide particular stuff, in future we would also like to select only the packages which are valid for given architecture. > Since this was largely new code entering > the > installer, it felt like as good a time as any. I don't think any of > the > cleanups pointed out were very difficult. Right now there is just not enough time to rewrite string handling. But this is just the introduction patchset, so it would be possible during testing, when we can actually see if our cleanup breaks stuff or not.. at the moment, we have no way how to test it properly. > I'd like to see comments from other people on the team regarding the > driver > disk patch set. Me too... and also on the question of possibly including updates.img on the driver disc. -- Martin Sivak Anaconda team / Brno, CZ _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
