On Wed, May 21, 2008 at 03:51:40PM -0700, Junio C Hamano wrote: > I think this is a wrong direction to go. > > We do not currently deal with broken installations, and "stow" is just one > easy way to install and keep a stale version. The right solution would be > to check if "Error.pm" we find on the system (be it installed by previous > incarnation of git or some other packages) works as expected, and refrain > from using it if it doesn't. Thank you for your response. The problem as I see it, is that the decision about whether the existing Error.pm "works as expected" is done at compile time. And git will break itself by repeated installs. Is it really valid to expect users to uninstall their current version of git before they can compile a new one correctly? For systems without a working Error.pm, this is currently how git behaves. - Chris -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
