On 02/25/2013 02:55 PM, Zdenek Pavlas wrote:
The problem is B has a post install script that calls an executable
installed by C.
Simple requires are always sufficient to guarantee install order,
unless there are dependency loops.
A dependency loop could be detected when ordering the transaction.
They are detected already of course, and snipped the best we can.
Packages participating in the loop must be installed essentially
"at the same time". Can't we do something like this, then?
1) %pre of B, then C
2) unpack B and C
3) %post of B, then C
Should work no worse than the current solution, IMO.
(scriptlet-to-executable requires would always work, at least)
That would help dealing with loops, but it would require huge changes to
how rpm does transactions. Also it has the potential to break some
scripts which expect the current exact semantics: testing for existence
of files (from other packages) could yield different results. Might well
be mostly a theoretical worry, but then scriptlets are known to do some
strange things :)
- Panu -
_______________________________________________
Yum-devel mailing list
Yum-devel@lists.baseurl.org
http://lists.baseurl.org/mailman/listinfo/yum-devel
