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

Re: Google Summer of Code 2013 (GSoC13)

From
Jeff King <peff@peff.net>
Date
Feb 18, 2013, 21:07 UTC
Message-ID
<20130218210709.GC27308@sigill.intra.peff.net>
In-Reply-To
<CALkWK0mKZLotuu7pEM_3Of3i6JzU12QV_pHxOZTUr22TOq3PeQ@mail.gmail.com>
On Tue, Feb 19, 2013 at 02:14:54AM +0530, Ramkumar Ramachandra wrote:
Show 9 quoted lines
> >  - assimilating the distro builds: "make deb-pkg", "make rpm-pkg",
> >    etc along the same lines as the linux kernel's script/package/,
> >    to help people get recent git installed when they want it
> 
> Overkill.  I just symlink to bin-wrapper/git from a place high up in
> my $PATH.  If anything, we should be making it easier for ourselves to
> run different versions of git right from $HOME, much like rbenv.
> System-wide installs are taken care of by the distribution package
> managers, and I doubt they need any help from us.

This is not related to GSoC anymore, but I think handling multiple versions is already pretty easy. You can just install to "$HOME/local/git/$TAGNAME" or similar, and then symlink the "bin/git" binary from there into your PATH as git.$TAGNAME (e.g., git.v1.7.8). Git already takes care of the messy bits, like making sure sub-programs are invoked from the same git version.

I already do this automagically with this script:
  https://github.com/peff/git/blob/meta/install/prefix

I just set "prefix" in the Makefile based on the script, and when I "make install" tags or topic branches, they go to the right place (and the "links" script in the same directory maintains the symlinks for me).

I never bothered to even submit those scripts to contrib, because I figured they were so specific to my setup, and to keeping dozens of git versions around (when debugging, it's nice to be able to check an old version's behavior without even having to build it).

Of course that has nothing to do with Jonathan's proposal. I do agree that it is pretty straightforward to just put $BUILD_DIR/bin-wrappers in your PATH and be done. I guess that doesn't cover manpages, though (but Real Programmers just read the source anyway, right?).

-Peff
Previous: Ramkumar RamachandraNext: Junio C Hamano
Message 27 of 47 in “Google Summer of Code 2013 (GSoC13)”
  1. Thomas RastFeb 18, 2013
  2. Jeff KingFeb 18, 2013
  3. Ramkumar RamachandraFeb 18, 2013
  4. Jeff KingFeb 18, 2013
  5. Ramkumar RamachandraFeb 18, 2013
  6. Jonathan NiederFeb 18, 2013
  7. Thomas RastFeb 18, 2013
  8. Ramkumar RamachandraFeb 19, 2013
  9. Jeff KingFeb 18, 2013
  10. Ramkumar RamachandraFeb 19, 2013
  11. Thomas RastFeb 18, 2013
  12. Jens LehmannFeb 18, 2013
  13. Junio C HamanoFeb 18, 2013
  14. Ramkumar RamachandraFeb 19, 2013
  15. Jonathan NiederFeb 19, 2013
  16. Ramkumar RamachandraFeb 19, 2013
  17. Thomas RastFeb 19, 2013
  18. Junio C HamanoFeb 19, 2013
  19. Thomas RastFeb 19, 2013
  20. Junio C HamanoFeb 19, 2013
  21. Ramkumar RamachandraFeb 19, 2013
  22. Junio C HamanoFeb 19, 2013
  23. Jonathan NiederFeb 18, 2013
  24. Jens LehmannFeb 18, 2013
  25. Christian CouderFeb 20, 2013
  26. Ramkumar RamachandraFeb 18, 2013
  27. Jeff KingFeb 18, 2013
  28. Junio C HamanoFeb 18, 2013
  29. Potential GSoC13 projects (Re: Google Summer of Code 2013 (GSoC13))Jonathan Nieder, Feb 18, 2013
  30. Duy NguyenFeb 19, 2013
  31. Jeff KingFeb 18, 2013
  32. Jonathan NiederFeb 18, 2013
  33. Shawn PearceFeb 20, 2013
  34. Christian CouderFeb 20, 2013
  35. Matthieu MoyFeb 20, 2013
  36. Thomas RastFeb 21, 2013
  37. Michael SchubertFeb 20, 2013
  38. Carlos Martín NietoFeb 21, 2013
  39. Florian AchleitnerFeb 25, 2013
  40. Junio C HamanoFeb 25, 2013
  41. Thomas RastFeb 18, 2013
  42. Ronan KeryellFeb 18, 2013
  43. Thomas RastFeb 18, 2013
  44. Ramkumar RamachandraFeb 18, 2013
  45. Thomas RastFeb 18, 2013
  46. Duy NguyenFeb 19, 2013
  47. Jaseem AbidFeb 26, 2013

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.