Hello Kent,
Kent Tong wrote:
> However, I'd like to deploy it to pilot group first. To avoid deploying to
> all users,
> I can't modify the existing <package>. It means I have to create a new
> <package>.
> If they have the same package id, then it will confuse wpkg, right? If they
> have
> different package ids, then wpkg will execute the install command instead of
> the upgrade command.
>
Yes. You could do the following
- replace the check, upgrade and remove commands from the existing
package "mypackage" by e.g.
<check type="file" condition="exists"
path="%SystemDrive%\netinst\logs\acrobat7.txt" />
<upgrade cmd='cmd /c echo ok
>%SystemDrive%\netinst\logs\acrobat7.txt ' >
<exit code="any" />
</upgrade>
<remove cmd='cmd /c del /q
%SystemDrive%\netinst\logs\acrobat7.txt ' >
<exit code="any" />
</remove>
(so the software is not changed in any way when upgrading/removing the
package)
- 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
- up to this point, nothing has changed to the clients but the text file
and the contents of wpkg.xml
- change the check/install/upgrade/remove entries in "mypackage2" and
test that at the test group
- when you are satisfied with your package, remove the assignment of
"mypackage" and assign "mypackage2" to the target group
> An approach to this problem is to let different groups see a different set
> of available
> packages, then the problem will be solved.
>
> Is there any way to do it?
>
Yes. You can set "base" as parameter or in config.xml, see
http://wpkg.org/WPKG_flags#Optional_parameters
But IMHO you would need a copy of your software repository, then.
Best regards,
Falko
|
|