Closed GoogleCodeExporter closed 8 years ago
> Invoking it with "/usr/bin/ruby $GEN_BRIDGE_METADATA" instead of
> just "$GEN_BRIDGE_METADATA" is an effective workaround.
Who guarantees that gen_bridge_metadata will always be a ruby script? It's an
Apple-provided tool; MacFUSE is
merely calling it.
Why is the workaround needed? Shouldn't the "new ruby" have at least the same
functionality as /usr/bin/ruby?
Original comment by si...@gmail.com
on 24 May 2008 at 6:20
> Who guarantees that gen_bridge_metadata will always be a ruby script? It's an
Apple-provided tool;
> MacFUSE is merely calling it.
Right, the real fix is for Apple to change the shebang line.
> Why is the workaround needed?
I don't know. I've only empirically observed that my build fails without it and
works with it.
> Shouldn't the "new ruby" have at least the same functionality as
/usr/bin/ruby?
It looks like Apple ships a bunch of gems that are not part of the basic Ruby
package.
Original comment by joshua.r...@gmail.com
on 25 May 2008 at 9:45
Right, so changing this in MacFUSE is not a good solution.
Original comment by si...@gmail.com
on 25 May 2008 at 5:29
Original issue reported on code.google.com by
joshua.r...@gmail.com
on 24 May 2008 at 9:51Attachments: