Seth Goldberg wrote:
> 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?
The trick is knowing the first version of system/library/install that
contains the bits necessary for the new install/beadm to function.
Since we don't have package versions that are addressable by anything more
fine-grained than the two-week builds, then you'd have to have something
like
depend type=require fmri=system/library/[email protected]
which prevents people trying to upgrade their ON bits from being able to do
so unless they're also connected to the nightly install repo, too -- at
least until they're using the RE build.
The problem with using that statement is that pkgdepend isn't yet very
savvy about dependencies that it generates that happen to be on the same
package for which you have a statically-declared dependency (bug 16026). I
don't think it'll break anything, but you'll end up with two dependencies.
Danek
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
