Sarah Jelinek wrote: > Jan Damborsky wrote: >> Jean McCormack wrote: >>> >>> The client has the following dependencies upon the CUD project. >>> >>> - The ability to collect data in user readable format along the way >>> during an install and retain that data for later output. >>> >>> - Provide defined points where stopping an install would work and >>> not modify the user system(in the case of dry run). >> >> For reference, with respect to the dry-run support, there is a >> requirement >> for particular modules to support that functionality - I can think at >> least about >> >> * Target Instantiation (dry run is supported except for BE part) >> * Transfer module >> * ICT >> >> Not sure if this requirement falls under CUD or should be captured >> at other place.
Note here that two of the modules Jan has pointed out that would support dryrun are write phases of install. If they support dryrun, I don't see why dryrun would be just considered a stopping point before phases that do writing. I think there's value in this type of dryrun support because you'd actually dry run through all or at least more of the code without doing a real install. thanks, -ethan >> > I think at this time it falls under CUD's scope. > > thanks, > sarah > ***** >> Jan >> >> _______________________________________________ >> caiman-discuss mailing list >> caiman-discuss at opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss > > _______________________________________________ > caiman-discuss mailing list > caiman-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
