git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Benoît Person" <benoit.person@ensimag.fr>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Matthieu Moy" <Matthieu.Moy@grenoble-inp.fr>,
	"Torsten Bögershausen" <tboegi@web.de>,
	"Git Mailing List" <git@vger.kernel.org>
Subject: Re: contrib/mw-to-git/Git/Mediawiki.pm
Date: Thu, 27 Jun 2013 19:54:36 +0200	[thread overview]
Message-ID: <CAETqRCif7K3MZiG4oMfnM-jps+KajDMYML4C5Hhy8eE7bj38xA@mail.gmail.com> (raw)
In-Reply-To: <7vzjubsbqj.fsf@alter.siamese.dyndns.org>

> Hmph.  Does it even need to be in-tree then?  Is it insufficient to
> run ../../git from that directory instead?
Well, the fact is we use Perl packages now (Git.pm and
Git::Mediawiki.pm in contrib/mw-to-git/Git/). The way we build perl
scripts in the toplevel's Makefile makes those packages accessible
only in $GITPERLLIB if it's defined and defaults to $INSTLIBDIR to
seek for installed version of those packages.

We use a bin-wrapper to define that $GITPERLLIB variable so that the
installed version gets bypassed by the one presents in the directory
defined in $GITPERLLIB.

> I just noticed that the script is not strictly a text file, ending
> with an incomplete line, by the way.
an incomplete line ?

  reply	other threads:[~2013-06-27 17:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-27 16:00 contrib/mw-to-git/Git/Mediawiki.pm Torsten Bögershausen
2013-06-27 16:25 ` contrib/mw-to-git/Git/Mediawiki.pm Benoît Person
2013-06-27 16:39   ` contrib/mw-to-git/Git/Mediawiki.pm Matthieu Moy
2013-06-27 17:29     ` contrib/mw-to-git/Git/Mediawiki.pm Junio C Hamano
2013-06-27 17:54       ` Benoît Person [this message]
2013-06-27 18:07         ` contrib/mw-to-git/Git/Mediawiki.pm Junio C Hamano
2013-06-27 17:28   ` contrib/mw-to-git/Git/Mediawiki.pm Junio C Hamano

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=CAETqRCif7K3MZiG4oMfnM-jps+KajDMYML4C5Hhy8eE7bj38xA@mail.gmail.com \
    --to=benoit.person@ensimag.fr \
    --cc=Matthieu.Moy@grenoble-inp.fr \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=tboegi@web.de \
    /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).