Excerpts from Peter Bonivart's message of Thu May 31 07:52:35 -0400 2012: > For almost every bad situation there's an equally bad alternative. > Pick your poison. :)
I agree with this and I think the current behaviour is actually the least bad option that we have. If we log the initial state (package set) and the proposed changes in some easily consumable (json, yaml) format, we could have a small tool that could diagnose a failed situation so that it's easy to see what needs to happen to recover. The CSWpkgloghooks could help with this somewhat but might not be a full solution. If it would help, I could augment it to make it more useful for cases like this. The alternative is to put this logging directly inside pkgutil and that is possibly better anyway. Thanks -Ben -- Ben Walton Systems Programmer - CHASS University of Toronto C:416.407.5610 | W:416.978.4302 _______________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers .:: This mailing list's archive is public. ::.
