Bart Smaalders wrote: > [EMAIL PROTECTED] wrote: >> So uninstall your incorporations before upgrading if your the new >> catalog doesn't have your previous versions, then? >> >> Hm. >> >> -j >> >> On Wed, Oct 15, 2008 at 09:17:54AM -0500, Shawn Walker wrote: >>> [EMAIL PROTECTED] wrote: >>>> This looks okay to me. Just to make sure I understand, 3704 just >>>> covers the fact that we have no top level handler for the >>>> InventoryException, correct? I didn't see anything that addressed >>>> optional dependency lookup, but I thought I'd ask just to be sure. >>> I asked Bart about the optional dependency loading, his response was: >>> >>> "Because if your new pkg plan requires installation of a package, >>> you need to make sure it's the right version wrt any optional >>> dependencies on that package." >>> >>> In short, I took that to mean I needed to leave the optional >>> dependency loading alone. >>> >>> This does mean that the client will fail, but at least it will fail >>> and the user will know why. >>> >>> Cheers, > > I experimented with this last night. If you make the repo that has only > the new packages the preferred repo and and the old one another > authority, it works.
So what are we saying here? Do I need to change anything? What I do know is this: repo1: foo, optional-dependency repo2: zoo 1) add both authorities to client 2) set repo2 preferred 3) install foo 4) unset-authority repo1 5) attempt to install foo or image-update and it will fail -- Shawn Walker _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
