Hi, If all goes well, I'll be pushing two wads -- one to ON and one to slim_source. The slim_source changes are vital to the proper functioning of the ON wad. The question is -- how do I express that in terms of a dependency so that when folks upgrade, they don't get surprised by that? Ideally, I'd like to express a "hard" dependency of install/beadm on a particular revision of system/library/install.-- is that the proper way to go about doing this, or is it mainly just a manual process of making sure the user has their repo set to point to an install-nightly repo that contains the new system/library/install package?
Thanks, --S _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
