Peter Tribble wrote:
I would expect that dependencies for a package from a given
publisher would first be searched for from that publisher.
Consider the following scenario: Package p1 from publisher X
depends on package p2, currently only available from publisher X.
A week later, the preferred publisher also releases package p2.
(Publisher X may be completely unaware of this.) If I then install p1,
it results in p2 being obtained from the preferred publisher, resulting
in a different system. This sort of unpredictable behaviour over
time drives sysadmins up the wall.
I can image whether a publisher being sitcky for dependency
resolution might be a configurable property; alternatively, packages
themselves might declare their dependency resolution policy.
So what if the preferred publisher already publishes
package p2? This would mean that any publisher could supplant
any package from a more preferred publisher that wasn't installed
yet with their own version, which seems... dubious.
- Bart
--
Bart Smaalders Solaris Kernel Performance
[email protected] http://blogs.sun.com/barts
"You will contribute more with mercurial than with thunderbird."
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
