Why not just create a new profile (called "pilot" or something) that contains the package to test, and then in your hosts.xml add this new profile to selected hosts that are to pilot the new package. You would still have to create a separate package entry with a unique id of course, but that's the way I would go about it.
On 9/23/08, Kent Tong <[EMAIL PROTECTED]> wrote: > > > > Falko Trojahn-2 wrote: > > > > - increase the revision number, so nothing on the existing clients is > > changed, only the text file will be created/removed > > > > - create a new, at least identical package, say "mypackage2"; assign it > > to the test group, remove "mypackage" from the same group > > > > > Hi Falko, > > Thanks for your reply! Take the "mypackage2" as an example, will it use > the same package id as "mypackage"? > > > > > ----- > -- > Kent Tong > Wicket tutorials freely available at http://www.agileskills2.org/EWDW > Axis2 tutorials freely available at http://www.agileskills2.org/DWSAA > -- > > View this message in context: > http://www.nabble.com/deploy-to-a-pilot-group-first--tp19620583p19622617.html > > Sent from the WPKG - Users mailing list archive at Nabble.com. > > ------------------------------------------------------------------------- > > wpkg-users mailing list archives >> > http://lists.wpkg.org/pipermail/wpkg-users/ > _______________________________________________ > wpkg-users mailing list > wpkg-users@lists.wpkg.org > http://lists.wpkg.org/mailman/listinfo/wpkg-users >
------------------------------------------------------------------------- wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ _______________________________________________ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
