Maintain pre-existing config files after installation of MacAthena packages about macathena

[tthoma24]

This blocks #9 and #10

[tthoma24]

I got part of an answer, which was to use post-activate step to copy the files with some TCL code like this:

post-destroot {
       file rename "${destroot}${prefix}/etc/ssh/sshd_config" "${destroot}${prefix}/etc/ssh/sshd_config.macathena.dist"
       file rename "${destroot}${prefix}/etc/ssh/ssh_config" "${destroot}${prefix}/etc/ssh/ssh_config.macathena.dist"
}
post-activate {
    if {![file exists "${prefix}/etc/ssh/sshd_config"]} {
        copy "${prefix}/etc/ssh/sshd_config.macathena.dist" "${prefix}/etc/ssh/sshd_config"
    }
    if {![file exists "${prefix}/etc/ssh/ssh_config"]} {
        copy "${prefix}/etc/ssh/ssh_config.macathena.dist" "${prefix}/etc/ssh/ssh_config"
}

This gets us part of the way there, in that we can check for the config file before copying ours in, but it doesn’t help us with uninstalls. For that, I think we would need to be doing the config copy during the destroot phase, but I’m stuck on how to actually achieve that, since this isn’t a compiled package where you would use make.

The downside is that according to http://www.mail-archive.com/[email protected]/msg31136.html, there is currently no provision for MacPorts to later remove files created that way. We'd also have to worry about config files that conflict with those provided by other ports, such as ssh_config and sshd_config conflicting with MacPorts provided OpenSSH..

I suppose, in the interim, we could just make people install Kerberos Extras from the IS&T website, or just stage the files in ${prefix}/etc/foo/foo.macathena.dist, and make a note for people to opy them into place. The reason I'm trying to avoid Kerberos Extras is I’d rather not depend on IS&T to continue packaging that, and it’s also an extra step that deviates from how DebAthena does it.