Rainer Meier wrote:
>
>
> Personally I prefer to specify that A is a dependency for B and then
> either
> assign A and B or just B to the profile which will assure that package A
> is
> installed first (since B depends on it).
>
>
Thats what I do (I add both packages but specify that B depends on A)
My concern is that I'm using the old method/syntax for my packages e.g.
<package
id="ps3"
name="Install Photostory 3"
revision="2"
reboot="false"
priority="100"
notify="false"
execute="once"
depends="mp10">
<install cmd='msiexec /i %PACKAGES%\ps3\PStory.msi /quiet /passive' />
<install cmd="%PACKAGES%\ps3\copyshortcut.bat" />
</package>
where the depends is an attribute as opposed to the new method/syntax where
the wiki now says it should be in its own element e.g
<package
id="ps3"
name="Install Photostory 3"
revision="2"
reboot="false"
priority="100"
notify="false"
execute="once">
<depends package-id="mp10" />
<install cmd='msiexec /i %PACKAGES%\ps3\PStory.msi /quiet /passive' />
<install cmd="%PACKAGES%\ps3\copyshortcut.bat" />
</package>
The main issue is how long will the old method be supported?
Also - is there a history of changelogs on the wiki - if not I'll try and
make ones up from the release docs.
regards
Simon
--
View this message in context: http://www.nabble.com/Package-Dependancy-tp25713729p25727501.html
Sent from the WPKG - Users mailing list archive at Nabble.com.
|