Re: Cooker upgrade still broken

On Jan 22, 2012, at 11:48 AM, Per Øyvind Karlsen wrote:

>> 
>> How? By force reloading all perl modules in a running application?
> Running application? urpmi isn't expected to be running, and when it's actually
> running, the required modules has already been loaded and shouldn't be
> a problem..
> 
> It's anyways solved by versioned dependencies on the required perl extensions.
> 

I needed to hear the info: thanks.

If versioned dependencies on perl extensions "works", that's fine.

The "correct" solution is likely unachievable and insoluble imho.

(aside)
Using net link to detect a SELinux configuration file change to
perform a callback to RPM terrifies me … the expectations
of package manager reliability are increasing.

See the bug reports here on cooker@, don't believe what I am saying.

hth

73 de Jeff