--- "Richard L. Hamilton" <[EMAIL PROTECTED]> wrote: > > > >so would i have to track patches and packages > > > >separately? > > > > > > The current scheme requires that; but that is > just > > > how > > > the patch tools are. There is no reason in the > > > underlying > > > package mechanism which forces this. > > > > so the pkg tools can handle updates or whatever > them > > patch commands do? > > Right now, a patch is usually one or more partial > packages that > overwrite the existing files (binaries, more often > than not), plus > optionally scripts to do "smart" stuff (merge > configuration changes, > for example). In that sense, they're not entirely > separate.
Well, will the pkg tools be able to update existing binaries and handle whatever else that is needed from whole new updated srv4 packages? Scrap patches. > > OTOH, very few outside of Sun build (or perhaps even > know how to build) > patches; for example, updates from blastwave replace > entire packages > (which can also have scripts with them to handle > smart actions). Less to track. > > If one were willing to have patches always involve > replacing entire > packages, then I suppose one could define a new sort > of patch as > simply a list of one or more packages and > corresponding versions, > that had to be updated together, in a specific > order, and perhaps > some optional additional action to be taken when all > of those updates > had completed successfully. Also, such a patch > should ideally include > machine-readable info as to what restarts, reboots, > or other impact-ful > actions might be required, so that the updating > tools could sensibly > interact with the user. And reboot requirements > should be conservative > (reboot if a scenario where that would be needed for > consistency could > reasonably be identified) but not excessive (i.e. > not just saying reboot > because we didn't want to take the trouble to > determine whether or > not it might be required). What are dependencies for then? No need for a new patch format. Just use the regular srv4 packages. The pkg update tool ought to be able to determine the whole chain of necessary packages that need to be updated when asked to update a package that has dependecies. Send instant messages to your online friends http://uk.messenger.yahoo.com _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
