On Thu, 2010-09-30 at 16:26 +0200, Radek Vykydal wrote: > The class is called RepoSpec. It should be backend independent, so perhaps it > will be moved to backend.py or even (new) repos.py. It will be used instead of > working directly (e.g. in UI steps) with extended YumRepository objects > (AnacondaYumRepository) making going back in UI possible without hacks (by > using new YumBackend object). > > Compared to YumRepository, it can hold anconda specific urls (nfs, cdrom, > nfsiso), repository type (method, kickstart, UI, driver disk, addon), > and info about setup status and cause of fail. Doesn't this mean you're going to be constantly having to add code whenever we add functionality or options to the yum repo objects? -sv _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
