Alok, I am not 100% sure. However, I thought that other images might want to version various components. Thus I put it into PrePkgImgMod class. It could go in the AIPrePkgImgMod class until such time as another image type needs or wants to version components. Is that you suggestion?
Thanks, John On 01/13/11 09:22 PM, Alok Aggarwal wrote:
Hi John, I just very briefly looked at the changes to DC included here - is there a reason why add_versions() is not defined within AIPrePkgImgMod? Will other image types also need to call this function in any other scenario? Alok ----- Original Message ----- From: [email protected] To: [email protected] Sent: Thursday, January 13, 2011 7:26:10 PM GMT -08:00 US/Canada Pacific Subject: Re: [caiman-discuss] webrev request for webserver design project - round 4 All, I have updated the webrev to match the current discussion and testing. The significant change is that there is now an impact on DC. Essentially I introduce a version file into the auto-install common package. This version file is copied into the generated ISO .image_file without the comments from the file. This was needed so that we could tell if the ISO being used for a service was old or new and act accordingly when setting up a new service. The new webrev is available at: http://cr.opensolaris.org/~johnfisc/webserver/webserver-design-4/ http://cr.opensolaris.org/~johnfisc/webserver/webserver-design-orig-4-diff/ The webrev that tracks the differences between review round 3 and round 4 is located at: http://cr.opensolaris.org/~johnfisc/webserver/webserver-design-diff-3-4/ Thanks, John _______________________________________________ caiman-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
_______________________________________________ caiman-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
