[EMAIL PROTECTED] wrote: > Tom, > I told you exactly what Stephen told me when I wrote the multiple > authority code the first time around. A package installed from the > preferred authority without explicit reference should follow whatever > the preferred authority is, even if it changes. Explicit authority > references freeze the package to the authority. > > The multiple authority code has been re-whacked a couple of times by > other people. I'm not sure how thoroughly they tested, or if they > changed any underlying assumptions. You'd have to ask them. >
To be strictly fair, the original design _had_ to be sticky wrt where packages originate, because each authority's package namespace was to be considered distinct. This has been abandoned, as it would require specification of authorities in all dependency actions - but authority names are a client-only abstraction. Today, packages are assumed to exist in a single name space across all authorities, and like-named packages from different authorities are assumed to be functionally equivalent. That said, the behavior of alerting users when packages are sourced from different authorities is planned, but not yet implemented. - 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
