Michael <barra_cuda <at> katamail.com> writes: > > When compiling, we check in perl/Makefile.PL if Error.pm is available. If not, > we use our Error.pm instead. So, after a "make install" the system does have > an Error.pm. This is fine, unless we are used to create an > rpm/deb/whatever-it-is by ourselves and install it with the system's package > manager: in this case, in fact, the git package we are building will have an > Error.pm only if the package currently installed does not. Of course, once we > install the new package, the next one won't ship Error.pm because > perl/Makefile.PL thinks it doesn't need to; but that's obviously wrong, since > the package manager will delete the old Error.pm when installing the new git > package. > > Apart from those making rpm/deb/whatever, I see another scenario where the current selection logic for systemwide Error.pm and private Error.pm may fail. This is if one uses GNU Stow for managing software that is not managed by the distro packaging system... whatever. A typical upgrade flow would be: You have Git version X installed in /usr/local/stow/Git-X and stowed. You now compile version X+1 of git, with prefix /usr/local/stow/Git-X+1 (here the current Error.pm logic thinks that there is no need for the private Error.pm since it finds an Error.pm -- only it is the Error.pm from the Git-X stowing) You install Git version X+1 in /usr/local/stow/Git-X+1 You unstow Git version X You stow Git version X+1 Git version X+1 fails because of missing Error.pm I.e. identical problem as with a true package manager. Problem is that the "private" Error.pm is put in a "public" location and not kept private with the current installation of Git. - 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