From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Junio C Hamano <gitster@pobox.com>
Cc: benoit.person@ensimag.fr, git@vger.kernel.org,
Celestin Matte <celestin.matte@ensimag.fr>
Subject: Re: [PATCH v6 2/5] git-remote-mediawiki: new git bin-wrapper for developement
Date: Thu, 27 Jun 2013 20:47:15 +0200 [thread overview]
Message-ID: <vpqppv7bdcc.fsf@anie.imag.fr> (raw)
In-Reply-To: <7vr4fnsafy.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Thu, 27 Jun 2013 10:57:53 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> As far as I can tell, the only real reason why you need this and
> cannot use ../../bin-wrappers/git directly is because the GITPERLLIB
> it gives you only points at ../../perl/blib/lib and not this
> directory.
Not only. You also need to have contrib/mw-to-git/ in the $PATH to be
able to run "git mw" and "git clone mediawiki::...".
> - Is there a reason you would not want to "install" whatever Perl
> modules you want to "use" via GITPERLLIB mechanism to
> ../../perl/blib/lib?
A previous version of the patch did something like this. This previous
iterations had issues, IIRC with the PATH, but they should be solvable
(and most likely independant from the $GITPERLLIB).
> Perhaps it will interfere with the real installation step in
> ../../perl/Makefile? If that is the case, then it is not a good idea,
> but otherwise, that would let you use ../../bin-wrappers/git as-is.
I do not like very much the idea of having the same target directory for
two Makefiles, but that's just instinctive suspicion, not a real
argument.
> - Perhaps we could do:
>
> GITPERLLIB="${GPLEXTRA+$GPLEXTRA:}@@BUILD_DIR@@/perl/blib/lib"
>
> in wrap-for-bin.sh, so that your instruction can become
>
> GPLEXTRA=$(pwd) ../../bin-wrappers/git whatever-mw-thing
You'd have to tweak the $PATH too, but that could be done by a very
small wrapper calling Git's bin-wrapper/git, like this:
GIT_ROOT_DIR=../../..
GIT_EXEC_PATH=$(cd "$(dirname "$0")" && cd ${GIT_ROOT_DIR} && pwd)
GIT_MEDIAWIKI="$GIT_EXEC_PATH"/contrib/mw-to-git
PATH="$GIT_MEDIAWIKI"/contrib/mw-to-git:"$PATH"
GPLEXTRA="$GIT_MEDIAWIKI"/contrib/mw-to-git
exec "${GIT_EXEC_PATH}/bin-wrappers/git" "$@"
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2013-06-27 18:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 17:37 [PATCH v6 0/5] git-remote-mediawiki: new tool to preview local changes without pushing benoit.person
2013-06-27 17:37 ` [PATCH v6 1/5] git-remote-mediawiki: Introduction of Git::Mediawiki.pm benoit.person
2013-06-27 17:37 ` [PATCH v6 2/5] git-remote-mediawiki: new git bin-wrapper for developement benoit.person
2013-06-27 17:57 ` Junio C Hamano
2013-06-27 18:47 ` Matthieu Moy [this message]
2013-06-27 18:53 ` Benoît Person
2013-06-27 22:21 ` Matthieu Moy
2013-06-29 11:09 ` Benoît Person
2013-07-01 7:46 ` Matthieu Moy
2013-06-27 17:37 ` [PATCH v6 3/5] git-remote-mediawiki: factoring code between git-remote-mediawiki and Git::Mediawiki benoit.person
2013-06-27 17:37 ` [PATCH v6 4/5] git-remote-mediawiki: Adding git-mw command benoit.person
2013-06-27 17:37 ` [PATCH v6 5/5] git-remote-mediawiki: Add preview subcommand into git mw benoit.person
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vpqppv7bdcc.fsf@anie.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=benoit.person@ensimag.fr \
--cc=celestin.matte@ensimag.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).