[Yum-devel] fallback on error'd dependencies

[Tim Lauridsen]

Tim Lauridsen wrote:
> seth vidal wrote:
>> Tim,
>>  Last week I noticed something you said that yumex does. You said that
>> if it encounters an unresolvable dependency on an update/upgrade that it
>> would remove the package causing the problem from the transaction and
>> try to finish with the rest of them. Is that correct?
>>   
> Yumex got at speciel "Safemode" option, if it is selected, then the 
> packages selected for install/update/remove is check one at a time in 
> the following way.
> The package i added to the Transaction Set by calling the appropiate 
> YumBase.install, .update or .remove.
> Then YumBase.buildTransaction() is called, if the return code is ==2 
> ,then the package is added to a
> good list.
> The Transaction Set is cleared and the process i repeat for all the 
> selected packages.
> When all packages has been checked for dependency problems, then the 
> good list is containing the packages there can be processed with out 
> dependency problems.
> All packages on the good list is added to Transaction Set and 
> processed as usual.
>> I'm curious if that code could be implemented as a mechanism off of the
>> depcheck callback that yum uses now.  I wouldn't want the default to
>> work that way (for all of the reasons I've already been through a bunch
>> of times) but it might be a functional option.
>>   
> If this kind of "feature" should be include in yum it could be 
> activated by a command line option.
>
> something like
>
> yum --predepcheck update.
>
> It could work by make a method in YumBase called 'preCheckDependencies'
>
> the function should take a list of packages as a parameter and some 
> kind of action command (install,remove,update) and then do a depcheck 
> on each package on the list and the return a list of
> packages with no problems.
>
> The YumCli could then call the preCheckDependencies if the 
> '--predepcheck' was set.
>
>> Would you be willing to take a look at that?
>>   
> If we define the way it should work, the i would give it a try to 
> implement it.
>
Here is a working copy of how it could be done, i have tested it with 
yum 2.6.1 (FC5),

Tim
-------------- next part --------------
A non-text attachment was scrubbed...
Name: predepcheck.py
Type: text/x-python
Size: 2557 bytes
Desc: not available
Url : http://lists.baseurl.org/pipermail/yum-devel/attachments/20060828/8d897608/attachment.py