Liane Praza wrote:
...
While it's currently not a strict requirement for putback (though it
will be over the coming months, and the ON cteam is already asking about
it), if upgrade fails from one supported OpenSolaris release to another,
a bug is likely to wind its way through the opensolaris team and back
onto your plate.
It's a good thing to make a product that we ship externally regularly
work, and the best time to do that is at putback.
If yes, is there a page documenting the steps and procedures and
requirements that
a developer needs to make the transition?
The instructions are fairly simple. IPS doesn't run any postinstall or
class-action scripts during package add or upgrade time. So, you don't
convert to IPS so much as make things work without requiring scripting
in package context.
Tools available to you to make that happen:
- Users and groups are added by actions in the IPS manifests. You
don't need to worry about these today as the OpenSolaris distribution
team takes care of translating your additions to IPS package actions.
- Similarly, driver bindings are handled by actions in IPS manifests
and today are added by the OpenSolaris distribution team.
Does the above statement include updating the ACPI tables for x86
and running the "add_drv" command for packages that contain new
device drivers (sparc and x86) ?
If a current SVr4 package already has postinstall scripts that do
those things but the OS dist. team has already converted those
things to IPS manifests for OpenSolaris, is there any additional
work to be done in the ON (SVR4) world to either remove the postinstalls
or ideally somehow integrate the IPS SMF manifest actions back into ON
so that the postinstall is not needed in either case?
thanks,
-Wyllys
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
