Re: [PATCH] svnrdump_sim: start the script with /usr/bin/env python
- From
Felipe Contreras <felipe.contreras@gmail.com>
- Date
- Nov 28, 2012, 19:19 UTC
- Message-ID
- <CAMP44s3YfLrL+74j5DOVVATK8GWEo1qHnmJDW5dLWJRxK_CVLQ@mail.gmail.com>
- In-Reply-To
- <7vmwy1hdgx.fsf@alter.siamese.dyndns.org>
On Wed, Nov 28, 2012 at 5:57 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Christian Couder <christian.couder@gmail.com> writes: > >> On Wed, Nov 28, 2012 at 9:03 AM, Felipe Contreras >> <felipe.contreras@gmail.com> wrote:
Show 8 quoted lines
>>> That works if somebody managed to export PYTHON_PATH, which very very >>> often is not the case for me. >> >> Yeah, and even if PYTHON_PATH is used, in t9020-remote-svn.sh, >> svnrdump.py is used as is. > > You need a fix for that; didn't I already say "you need a bit more > than that"?
I disagree. Most of the contrib scripts are expected to be used as they are. There's no step in the Makefile that will convert them, and it's up to each distribution to decide what to do with them. This is what Arch Linux does:
# more contrib stuff
cp -a ./contrib/* $pkgdir/usr/share/git/
# scripts are for python 2.x
sed -i 's|#![ ]*/usr/bin/env python|#!/usr/bin/env python2|' \
$(find "$pkgdir" -name '*.py') \
"$pkgdir"/usr/lib/git-core/git-p4 \
"$pkgdir"/usr/share/git/gitview/gitviewAt some point we might decide to change this, but at the moment contrib scripts are pretty much stand-alone.
Cheers.
-- Felipe Contreras