BUG: asciidoc-7.1.2 is broken on Tiger

[dreamind@…]

Hi,

asciidoc seems to use a hardcoded #!/opt/DarwinPorts/bin/python path (for me DarwinPorts is in /opt/DarwinPorts) on Tiger.

But on Tiger it somehow does not depend on a DarwinPorts installed python, it uses the system python which is in /usr/bin/python.

So why not use #!/usr/bin/env python ?

Thanks.

[yaseppochi (Stephen J. Turnbull)]

(In reply to comment #0)

asciidoc seems to use a hardcoded #!/opt/DarwinPorts/bin/python path (for me DarwinPorts is in /opt/DarwinPorts) on Tiger.

Still broken as of 2006-08-15. This is really confusing if asciidoc gets pulled in as a dependency (eg, for git-core +doc) because the build craps out with

make[1]: asciidoc: Command not found

but of course it's not make's fault:

$ asciidoc -bash: /opt/local/bin/asciidoc: /opt/local/bin/python: bad interpreter: No such file or directory

[markd@…]

Assigning to maintainer. But it look to me like asciidoc is set to look for Dp's python at /opt/local/bin/python

reinplace "s|^{#!/usr/bin/env python|#!${prefix}/bin/python|" \}

${destroot}${prefix}/bin/${name} \

but it doesn't list it as a dependency. If you install DP's python I think it would work. I just installed it and don't get that error.

[blb@…]

No longer maintaining this port.

[markd@…]

So isn't a dependecy on DP's Python all that is require here?

[cssdev]

The ​AsciiDoc Installation page mentions that Python 2.3 or newer is required, but is there something specific that prevents asciidoc from working with the built-in python interpreter? I also note that version 8.0.0 was recently released.

[markd@…]

It isn't that it can't use Apple's libraries, it is that doing so *in general* is against the design philosophy of MacPorts. See section "Why is MacPorts using it's own libraries?" here: ​http://trac.macosforge.org/projects/macports/wiki/FAQ. It degrades consistency and predictability of MacPorts installed software, and makes it likely that some Apple system updates will cause your MacPorts software to break. But if it isn't feasible for any reason to have a port use MacPorts libraries then exceptions are of course made.

So it seems to me that the only problem here is that MacPorts' python is not listed as a dependency, and no one has offered a reason why this port should depend on Apple's Python. Barring some clear reason why Apple's python should be depended on, I think that the MacPorts python should be added as a dependency and this bug could be closed.

The update to 8.0.0 is quite easy to do but it would be nice if someone that knows the app would check it out ok it since it is a major update. I'll attach the patch to update it.

[markd@…]

Patch to update portfile to 8.0.0

[markd@…]

Added MacPorts' python dependency.