On Thu, 2007-05-03 at 09:18 +0200, Tim Lauridsen wrote: > +1, It is implemented as a class, so i could be move into yum, then it > could be called by the yum-cli and the gui's. > A more advanced approach is to build it into the depsolver, so it > contruct a list packages with problems, there can be skipped > if the option is set. It could be made default like in apt-get, > reporting that the following packages could not be updated because for > dep errors.
hesitant to make that a default, truth be told, though. > > 4. in general look at the plugins and utils and see what features would > > be better off in the base code or vice-versa. Is there core code that > > should really go live in a plugin > > > Sound good to me, maybe some priorities or protectbase stuff, to make it > easier to protect base packages from being overwritten > på other repos. I'd want to see an implementation that doesn't make excludePackages() look insane. > > 5. yum-gate - take the code that rnorwood posted and maybe work on > > making it more releasable for folks to use as an authenticated yum repo. > > Alternatively, look at one of the other system-config-mgmt tools to work > > for that. > > > I have just got some patches from another IBM'er, that make changes to > UG and yum to support a client side SSL cert. I will post it on the list. I liked those patches. If we could document how to use that feature + apache cleanly it might work out well. Curiously, is it possible to auth via ssl client cert without connecting to an ssl site? That would make the payloads lighter but strongly authenticated. > * Switch from CVS to a distributed SCM like mercurial. has hg won the distributed scm wars? > * yum list vendors > List install packages and the rpm vendors, there have been a lot of > discussions on the EPEL list, about repotag as a way to locate the > source of the packages, because the basic packages tools like yum > don't show it in a simple way. Can't repoquery do this? > * make some generic callback handler in yumbase there can be subcased by > applications using yum API. > Example: > http://yumex.svn.sourceforge.net/viewvc/yumex/trunk/yumex/src/yumgui/callbacks.py?view=markup. > > * yumlets :-) > A sort of metapackage that contains a collection of packages and yum > metadat, a sort of mini repo compressed into a single file. > It could be very useful in there part of world where the broadband > connection is very expensive. > > It could work like this. > > yum install /path/or/url/to/yumlet. > > Then yum would extract the packages and metadata in at special local > yumlets repo cache and install the packages from there. That's what debarishi is working on, as james mentioned, i think. I'm still not sure how exactly that helps a user, though. -sv _______________________________________________ Yum-devel mailing list [email protected] https://lists.dulug.duke.edu/mailman/listinfo/yum-devel
