On Tuesday 04 August 2009 00:08:48 Mike Edenfield wrote:
> > I have the identical file, it works here.
>
> That's very odd, as everything I've read over the past hour indicates
> that it's not supposed to work if you put a shell script in that line,
> but that's clearly not always true.
I didn't diff it, just compared yours and mine visually
> What's the #! line in your /usr/bin/emerge file?
$ head /usr/bin/emerge
#!/usr/bin/python
# Copyright 2006-2009 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Id: emerge 13131 2009-03-18 01:43:41Z zmedico $
import sys
# This block ensures that ^C interrupts are handled quietly.
try:
import signal
>
> > Your original post has a "X connection to localhost:11.0 broken" error,
> > which is mighty unusual. The error is common enough, but has nothing to
> > do with python.
>
> I know where that particular error is coming from. The first
> non-comment line in /usr/bin/emerge is "import sys". Since bash is
> interpreting the script instead of python, when it gets to that line, it
> runs ImageMagick's "import" command. It just indicates that bash
> ignored the #! line and kept going.
Ah, now stuff makes sense, like your reference to ImageMagick
> The bug Remy sent me to did have two working solutions: replacing the
> shell script with a symlink, or replacing "#!/usr/bin/python" with
> "#!/usr/bin/env python" in emerge/ebuild, both of which point the #!
> line at a real executable. I'm now curious why that shell script works
> for anyone.
--
alan dot mckinnon at gmail dot com
