Kent Tong wrote: > 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? My approach has been: - Systems which get pilot packages are configured on the client to use \\SERVER\wpkg\testing as the base directory. - Systems which don't get pilot packages are configured on the client to use \\SERVER\wpkg\updates as the base directory. - Changes are made to \\SERVER\wpkg\testing and copied across to \\SERVER\wpkg\updates when I'm happy that they won't break anything. This requires that you are fairly disciplined at either committing or rolling back your changes when appropriate or you'll probably get very confused but this is probably a good idea with such a scheme anyway. My technique has the bonus that it drastically reduces the risk of typos between pilot and live, at the cost of requiring two subtly different client configurations. -- James Cort IT Manager U4EA Technologies Ltd. -- U4EA Technologies http://www.u4eatech.com |