coapp-developers team mailing list archive

[Adam Baxter <voltagex@xxxxxxxxxxxx>]

Hi,
Do you think each package type should have pre and post install actions?

For example,
* an executable package might register itself to the Games Explorer on
Vista/7 after installation
* a source package might need a very specific folder structure
* an executable might require non-CoApp resources to run, for example an
activation key or data files from a CD (think a free application with
non-free addons)
* a package that is saving some configuration details to the registry (not
recommended, limits portable installations)
and so on

If so, what would be the best way to document this? I was just going to add
a "Pre & Post Install" section to each package blueprint.

--Adam