Figured I'd post a few votes on these as one of the owners of a large environment using yum. I love using the hard work going on here as an example of how open source produces a better product than proprietary processes.
Keep up the good work! On 5/3/07, seth vidal <[EMAIL PROTECTED]> wrote:
Here's the list I've put together from what some folks have posted. This is not necessarily complete but it is the set of things which I find particular interesting: - use tolerant config option to step around problem pkgs in a transaction
+1 More error checking and / or ways to make sure "yum -y <command> " in my cron scripts at least completes most of the package installs / updates would help a great deal with cleaning up machines in bad states. At least the machines would be getting some of their automatic updates instead of being totally in the cold till someone had time to intervene manually. - gpg/cert/sig check on repomd.xml
- client-side ssl certs for repos
+1 I'd like to start distributing proprietary packages in our environment. This would go a long way towards allowing me to do this. We can control access to the repositories from the web server side if yum is able to send some type of authentication identifying the host. However if the repo does fail authentication yum would need to continue as if it didn't exist instead of failing as it currently does now. - docs for this +2 Just a couple of wiki pages would be more than enough. I'm pretty sure I can bite myself - switch from cvs to $SCM (git, hg)
- more generic rpm/transaction callback interface - not at the cli level. - pattern= in install(), update(), remove() - per-item pre and post transaction plugin hooks
+1 Would these be possible in the spec file or repository level or would they have to be set when yum was called. We ran into a problem with a postun script where a rm <dir> wasn't escaped to only run on removal. You can imaging how well updates were going after that hit the repos. . . Manually sshing to 8000+ machines wasn't on our list of things to do that day. Being able to clean up the existing package in the posttrans of the fixed one would have been a huge help. - transaction event database? - as a plugin?
- recursive/unused dep-removal in yum
I just want this for my own box. I need to clean up some space. ;-) - merge in some commonly-used plugins
- protectbase? - installonlyn?
+1 we do have several packages it would be helpful to keep multiple versions around. - priorities? +1 Groups here are already starting to deploy their own yum repos here. I think its great that they are but we have to keep the base repos intact to keep them supportable. Although it might be nice if the default priority was 50 or 75. Its easier to lower the priority on one repo than it is to raise the priority on five or six. Meh, maybe I'm just lazy. ;-) - fastestmirors?
- allowdowngrade?
I still haven't figure out how to make this work. Where should I be looking for documentation. - changelog? I love this plugin. I don't update without it! - tsflags?
- yum list vendors
I'd like to see a little more information in the update output in general. I like how apt will show you the installed version and the new version its being updated too. I would like to see the vendors tag there as well but its simply a nice to have. Russell ---- Russell Harrison Systems Administrator -- Linux Desktops Cisco Systems, Inc.
_______________________________________________ Yum-devel mailing list [email protected] https://lists.dulug.duke.edu/mailman/listinfo/yum-devel
