From: Jeff King <peff@peff.net>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: "Jonathan Nieder" <jrnieder@gmail.com>,
"Thomas Rast" <trast@inf.ethz.ch>,
git@vger.kernel.org, "Shawn Pearce" <spearce@spearce.org>,
"Jakub Narebski" <jnareb@gmail.com>,
"Christian Couder" <christian.couder@gmail.com>,
"Pat Thoyts" <patthoyts@users.sourceforge.net>,
"Paul Mackerras" <paulus@samba.org>,
"Carlos Martín Nieto" <cmn@elego.de>,
"Thomas Gummerer" <t.gummerer@gmail.com>,
"David Barr" <b@rr-dav.id.au>,
"Jens Lehmann" <Jens.Lehmann@web.de>,
"Nguyen Thai Ngoc Duy" <pclouds@gmail.com>
Subject: Re: Google Summer of Code 2013 (GSoC13)
Date: Mon, 18 Feb 2013 16:07:09 -0500 [thread overview]
Message-ID: <20130218210709.GC27308@sigill.intra.peff.net> (raw)
In-Reply-To: <CALkWK0mKZLotuu7pEM_3Of3i6JzU12QV_pHxOZTUr22TOq3PeQ@mail.gmail.com>
On Tue, Feb 19, 2013 at 02:14:54AM +0530, Ramkumar Ramachandra wrote:
> > - 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
next prev parent reply other threads:[~2013-02-18 21:07 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 17:23 Google Summer of Code 2013 (GSoC13) Thomas Rast
2013-02-18 17:42 ` Jeff King
2013-02-18 18:44 ` Ramkumar Ramachandra
2013-02-18 18:58 ` Jeff King
2013-02-18 19:45 ` Ramkumar Ramachandra
2013-02-18 19:57 ` Jonathan Nieder
2013-02-18 20:03 ` Thomas Rast
2013-02-19 7:51 ` Ramkumar Ramachandra
2013-02-18 21:13 ` Jeff King
2013-02-19 9:00 ` Ramkumar Ramachandra
2013-02-18 19:45 ` Thomas Rast
2013-02-18 20:01 ` Jens Lehmann
2013-02-18 22:32 ` Junio C Hamano
2013-02-19 7:08 ` Ramkumar Ramachandra
2013-02-19 7:25 ` Jonathan Nieder
2013-02-19 8:12 ` Ramkumar Ramachandra
2013-02-19 8:41 ` Thomas Rast
2013-02-19 16:29 ` Junio C Hamano
2013-02-19 16:39 ` Thomas Rast
2013-02-19 7:31 ` Junio C Hamano
2013-02-19 8:22 ` Ramkumar Ramachandra
2013-02-19 16:32 ` Junio C Hamano
2013-02-18 19:34 ` Jonathan Nieder
2013-02-18 20:02 ` Jens Lehmann
2013-02-20 6:17 ` Christian Couder
2013-02-18 20:44 ` Ramkumar Ramachandra
2013-02-18 21:07 ` Jeff King [this message]
2013-02-18 22:37 ` Junio C Hamano
2013-02-18 21:11 ` Potential GSoC13 projects (Re: Google Summer of Code 2013 (GSoC13)) Jonathan Nieder
2013-02-19 1:23 ` Duy Nguyen
2013-02-18 20:55 ` Google Summer of Code 2013 (GSoC13) Jeff King
2013-02-18 23:03 ` Jonathan Nieder
2013-02-20 6:50 ` Shawn Pearce
2013-02-20 12:07 ` Christian Couder
2013-02-20 12:26 ` Matthieu Moy
2013-02-21 15:41 ` Thomas Rast
2013-02-20 19:48 ` Michael Schubert
2013-02-21 14:29 ` Carlos Martín Nieto
2013-02-25 9:12 ` Florian Achleitner
2013-02-25 17:44 ` Junio C Hamano
2013-02-18 17:46 ` Thomas Rast
2013-02-18 18:02 ` Ronan Keryell
2013-02-18 19:48 ` Thomas Rast
2013-02-18 18:13 ` Ramkumar Ramachandra
2013-02-18 19:53 ` Thomas Rast
2013-02-19 1:17 ` Duy Nguyen
2013-02-26 4:59 ` Jaseem Abid
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130218210709.GC27308@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=Jens.Lehmann@web.de \
--cc=artagnon@gmail.com \
--cc=b@rr-dav.id.au \
--cc=christian.couder@gmail.com \
--cc=cmn@elego.de \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=jrnieder@gmail.com \
--cc=patthoyts@users.sourceforge.net \
--cc=paulus@samba.org \
--cc=pclouds@gmail.com \
--cc=spearce@spearce.org \
--cc=t.gummerer@gmail.com \
--cc=trast@inf.ethz.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).