Userland webrev:
 http://cr.opensolaris.org/~alanc/7016849/

ON webrev (internal only):
 http://jurassic.us.oracle.com/net/also/export/alanc/onnv-clone/7052095/

(If you do review, please let me know which of the two I can list you as
 reviewing in the respective RTI's.)

The userland side is a bit unusual - the upstream repos do not provide
stable download URL's, simply the latest daily snapshots.   Since these
are simple text files, instead of trying to make some sort of stable
download mirror, I've just gone with checking them into the gate, much
as they were in ON.   Future updates (which I should be doing approximately
once a quarter, as I've been doing for Solaris 10 the past few years)
would just be checking in new snapshots instead of updating version numbers
for new packages to download.

The ON side simply deletes the existing files, as well as ensuring the
package dependencies are set correctly in the hal & ddu packages that
read these files in.

I believe that this won't require any sort of flag day, just coordinated
putback to both consolidations in the same build (hopefully in 169).

Those who update to on-nightly but not userland-nightly would simply see
hardware-registry become unconstrained by osnet-incorporation, but the
package dependency in the hal package would keep the installed copy around.

Those who update to userland-nightly would see that the new hardware-registry
from userland isn't installed until their osnet-incorporation is upgraded to
a build (either from on-nightly or the WOS biweekly) that no longer constrains
it, but as the files are identical, unless they're specifically trying to test
the new package, they shouldn't care.

Those who are trying to test can either create a modified osnet-incorporation
similar to the sfw-incorporations covered in the Userland testing instructions
or use the one from the on-nightly repo once that side is integrated.

-- 
        -Alan Coopersmith-        [email protected]
         Oracle Solaris Platform Engineering: X Window System

_______________________________________________
on-ips-dev mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/on-ips-dev

Reply via email to