On Fri, 2005-07-22 at 10:52 +0200, Christian Haugan Toldnes wrote: > It's just swup trying to be wise and keep the system as up to date as > possible. > > Both ntp and openldap requires /usr/bin/perl, and php-ldap requires > openldap. > > What swup does when you issue the command "swup --upgrade perl" is to > check if a newer version of perl is available. If it is, swup then > checks if any other installed package that requires perl has an > available update. If it has one, that's also selected for upgrade, and > so on. > > The '--local-first' switch might force swup to only upgrade what's > needed, but since it was not included for this specific situation, I'm > not sure that it will do anything useful. :)
Okay, this implied forced update poses a problem for me with the way I do things. I have a script that notifies me via email if there are updates. Then I login to the machine and do a --upgrade --poll-only to see what's available. Depending on what's running on the machine, I may not want or be able to upgrade everything that needs an update, due to scheduled maintenance windows and services running or how I delicate I feel the upgrade process is for a certain set of RPMs. For example, if I know that mysql is dependent on perl because there are scripts that I never use in the mysql rpm written in perl, I should be able to upgrade those independently (this mysql<->perl dep is an example). (In fact, I prefer to upgrade mysql independently of all other updates because I've gotten bitten before with the upgrade nuking the mysql data directories (back on tsl-1.5, I think), so I like to pay closer attention to the upgrade process with the critical services. This also has to be done after hours, but I'd rather not hold up all non-critical updates until after hours, and actually spread out my updating over time to lessen the chance of a much larger failure. I suppose we can debate the legitimacy of this way of doing things, but this is not what this post is for). Is there some way to force it do what I mean, rather than trying to be smart for me, and only upgrade the packages given on the command line, even if that might not be a good idea? I don't understand what the --local-first option would do in this case. Is it safe to use here, considering it's listed under DEBUG OPTIONS in swup --help? (--local-first is not mentioned in the man page installed with swup-2.7.9-2tr, where I was hoping there was more detailed information). Is there some kind of "loose" binding dependency that could be used for things like this when building the RPM? Or maybe relying on major versions rather than full version strings in the Requires: clause? Especially for support scripts? I suppose the rpm-find-requires scripts (or whatever they are called) would have to modified to support that. -- Andy Bakun <[EMAIL PROTECTED]> _______________________________________________ tsl-discuss mailing list [email protected] http://lists.trustix.org/mailman/listinfo/tsl-discuss
