example config files: destroot or activate?

[Bradley Giesbrecht]

On Mar 6, 2012, at 10:27 AM, Jeremy Lavergne wrote:

>> Yes, use post-activate to achieve what you want.
>> 
>> If the file is "installed" by MacPorts, meaning "port contents name" lists the file, then the file will be removed on deactivate.
> 
> This is what I feared: before the buildbot and images-and-archives merged in, we detected when to install files in post-destroot.

I have not read the code so I may be wrong about which phase a ports files are registered but I am confident that you do not want your file in "port contents".

> Only users who edited the default files were impacted, but now anyone who has a config file and installs from an archive is also at risk (buildbot built an archive without dirty config files laying around).

Could you add a checksum test to pre-deactivate or pre-fetch and copy the file on checksum match failure?
This might help with upgrade.


Regards,
Bradley Giesbrecht (pixilla)