git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH resend] perl/Makefile.PL: teach makefiles about possible old Error.pm files

From
CFChris Frey <cdfrey@foursquare.net>
Date
May 21, 2008, 23:56 UTC
Message-ID
<20080521235647.GA21340@foursquare.net>
In-Reply-To
<7vzlqjz2wz.fsf@gitster.siamese.dyndns.org>
On Wed, May 21, 2008 at 03:51:40PM -0700, Junio C Hamano wrote:
Show 7 quoted lines
> 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
Previous: Junio C HamanoNext: Johannes Schindelin
Message 5 of 11 in “perl/Makefile.PL: teach makefiles about possible old Error.pm files”
  1. perl/Makefile.PL: teach makefiles about possible old Error.pm filesChris Frey, May 17, 2008
  2. Chris FreyMay 17, 2008
  3. perl/Makefile.PL: teach makefiles about possible old Error.pm filesChris Frey, May 21, 2008
  4. Junio C HamanoMay 21, 2008
  5. Chris FreyMay 21, 2008
  6. Johannes SchindelinMay 22, 2008
  7. Chris FreyMay 22, 2008
  8. Junio C HamanoMay 22, 2008
  9. Chris FreyMay 22, 2008
  10. INSTALL: explain Error.pm dependencyChris Frey, May 23, 2008
  11. Sverre RabbelierMay 22, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.