On 24.08.2010, at 01:44, Levente Uzonyi wrote:

> On Tue, 24 Aug 2010, Bert Freudenberg wrote:
> 
>> On 24.08.2010, at 00:34, Levente Uzonyi wrote:
>> 
>>> On Tue, 24 Aug 2010, Bert Freudenberg wrote:
>>> 
>>>> On 24.08.2010, at 00:03, Levente Uzonyi wrote:
>>>> 
>>>>> The problem with updating after unloading is that the updater mechanism has no information of package dependencies, so it will try to load packages randomly which obviously won't work.
>>>> 
>>>> It does not load packages randomly, but in the order defined in the update config map.
>>> 
>>> That's right, but it's still random from the package dependency POV.
>> 
>> What makes you think so? The order is chosen (manually) so that dependent packages are loaded before depending packages.
> 
> If that would be the case, then updating an "unloaded" image would reload all unloaded packages.

Indeed. That's how it is supposed to work.

> But that doesn't work. For example 311Deprecated depends on Traits, but Traits is at the end of the list while 311Deprecated is the first non-dummy package.

Then, obviously, the update map is wrong :)

- Bert -