Peter Tribble wrote:
I can see how it works - and works well - in cases where the only correct version of the constructed file is that built up be self-assembly. But what if the file were an administrative file that could be edited by an administrator (either directly or through some tool such as cfengine)? How do you ensure that subsequent re-assembly of the file doesn't lose the external edits?
In this case, we need to be a little more clever... but not any more clever than we needed to be w/ postinstall scripts, which deal w/ the same three-way merge problem. You can either never merge from scratch again (eg work out which files have changed and just merge in those), or determine which files have been removed (we're considering an tag to make saving these sorts of files easy) and figure out the diffs that way. Postinstall scripts have the same issues; generally, most toss user input or don't implement removal when a package is uninstalled. - Bart -- Bart Smaalders Solaris Kernel Performance [email protected] http://blogs.sun.com/barts "You will contribute more with mercurial than with thunderbird." _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
