sbotsford wrote: > Tomasz Chmielewski wrote: >> sbotsford wrote: >>> >>> Question: for the developers: >>> 1. What determines whether a piece of information is embedded as an >>> attribute or as a separate tag. Eg: Check has 3 attributes, but >>> install has only command. >> >> It's up to you, as a system administrator, to determine how many >> checks you have and how many install commands you use (you can have >> more than one install command - see "silent installers" in the wiki >> for examples). >> >> > > Hmm. Didn't make myself clear. This is not a question on how to do > something, but one of why it is done in a particular way. > > Let me try again. > > The package tag has 5 attributes, each which can take a value. > The install tag has the command attribute, and an additional tag, exit. > Why is exit a separate tag, instead of being an attribute of install? > > More generally, what is the reason to encode data as an attribute > instead of a tag? Perhaps because you didn't invent WPKG first :) Seriously, check for example this installer: http://wpkg.org/index.php/Microsoft_Windows_Journal_Viewer <install cmd='\\server\share\updates\journalviewer\enu\setup.exe /q /c:"msiexec /l* %SystemDrive%\netinst\logs\journalviewer.txt /i ""Microsoft Windows Journal Viewer.msi"" /qn"' > <exit code="194" reboot="true" /> <exit code="1603" /> <exit code="3010" reboot="true" /> </install> -- Tomasz Chmielewski http://wpkg.org wpkg-users mailing list wpkg-users at lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users |