On Thu, Dec 10, 2015 at 12:58:41PM +0100, Reindl Harald wrote:
Am 10.12.2015 um 12:53 schrieb Rex Dieter:
>Florian Weimer wrote:
>
>>When a %post scriptlet runs, is it guaranteed that the Requires:
>>dependencies have been unpacked? I understand that for cycle-breaking
>>purposes, it may not be true that the scriptlets for dependencies have
>>run. But are the files already there?
>
>I think the answer in general is no, you cannot be guaranteed that Requires:
>get installed before %post runs. That's one reason why Requires(post)
>exists
sounds terrible
what's with the "Require" of a "Requires(post)" to guarantee
that
the "Requires(post)" *really* work sucessful? sounds fragile
Relax, the difference between Requires and Requires(post) is rather
small. It only makes a difference when breaking dependency cycles,
and in that case there's no correct solution anyway.
I.e. if package A has "Requires: B" and package B has
"Requires(post): A", there's really no correct order.
"First A then B" is incorrect because "A Requires B" may mean that
B must by 100% installed (with postinstall scriptlets) for A to work,
thus A may still not work in B's post script.
Cheers,
Michael.
--
Michael Schroeder mls(a)suse.de
SUSE LINUX GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}