[wpkg-users] Excluding particular OS and architecture types from patch application

heiko.helmle at horiba.com heiko.helmle at horiba.com
Thu Apr 29 09:23:28 CEST 2010


> > Do you mean something along the lines
> > <package package-id="7zip" OSGreaterorequal="6.1" />
> > That is interesting, however i think conceptually the OS and arch
> > dependency belongs to the package itself rather than its profile
> > assignment.
> 
> Yes, something like this.
> 
> I disagree that packages should be OS dependent. The vast majority of 
software
> packages run on any Windows version available. The decision not to 
> install it on specific Windows version belongs more to the profile than 
to the package. Sure
> there are some packages which should not be applied on specific OS 
> versions but
> if the profile supports limiting the package assignment to OS it canbe 
handled
> perfectly on profile level.

Hmm... what do you think of adding conditionals to the <install>-command 
utilizing the check syntax that's already there anyways...

something like this

<install cmd='install-x86' conditional='true' >
        <check type="registry" condition="equals" 
path='HKLM\SYSTEM\CurrentControlSet\Control\Session 
Manager\Environment\PROCESSOR_ARCHITECTURE' value="x86" />
</install>
<install cmd='install-x64' conditional='true' >
        <check type="registry" condition="equals" 
path='HKLM\SYSTEM\CurrentControlSet\Control\Session 
Manager\Environment\PROCESSOR_ARCHITECTURE' value="AMD64" />
</install>

This doesn't change the behaviour of scripts already deployed and might 
add only little code to wpkg (though I didn't look at that part of the 
code). And it's far less complicated.

this of course means (again) admins writing proper checks :)

Maybe adding some easy 'shortcut checks' could also make life easier (and 
xmls smaller), like a check type "arch" or "winversion".

<check type="arch" condition="equals" value="AMD64" />
<check type="winversion" condition='versiongreaterorequal' value="6.0"/>

I know these are easily replaced by registry check or cmd script, so I 
consider this (and the installchecks) as 'nice to have'. (just an idea 
floating around)

Best Regards
        Heiko Helmle
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wpkg.org/pipermail/wpkg-users/attachments/20100429/32e6a34e/attachment-0002.html>


More information about the wpkg-users mailing list