[MacPorts] #27794: New port: ige-mac-bundler 0.6.0
MacPorts
noreply at macports.org
Mon Dec 27 10:21:40 PST 2010
#27794: New port: ige-mac-bundler 0.6.0
---------------------------+------------------------------------------------
Reporter: mike@… | Owner: ryandesign@…
Type: submission | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version:
Keywords: | Port: ige-mac-bundler
---------------------------+------------------------------------------------
Comment(by ryandesign@…):
Committed in r74669 with these changes:
* reformatted whitespace
* removed commented-out dependencies
* removed md5 checksum which I consider to be obsolete
* changed "configure {}" to "use_configure no" (see "port lint")
* replaced "exec cp -R" with "copy"
* tweaked livecheck settings
I also meant to indicate that this software does not install any
architecture-specific files, but I forgot; I committed that change in
r74670.
However, I don't think the software works, because:
1. The script ${prefix}/bin/ige-mac-bundler begins with:
{{{
#!/usr/bin/env python
}}}
That means it will run using whatever python the user happens to have
selected, or Mac OS X's python if the user hasn't selected one. Instead,
the port should declare a dependency on a specific version of python (2.7,
I guess, since that's the python into whose directory you've copied the
files) and use that specific version of python in the shebang line.
2. Next, the script reads:
{{{
sys.path.insert(0, '/i386-10.6-mp/var/macports/build
/_Users_rschmidt_macports_dports_devel_ige-mac-bundler/work/ige-mac-
bundler-0.6.0')
}}}
That path does not exist after the port has been installed; that's the
work directory that MacPorts (by default) cleans up after a successful
installation. Trying to run the script gives me:
{{{
Traceback (most recent call last):
File "/i386-10.6-mp/bin/ige-mac-bundler", line 5, in <module>
import bundler.main
ImportError: No module named bundler.main
}}}
So this path needs to be changed to something else before installation.
Can you attach a patch to address these issues?
--
Ticket URL: <https://trac.macports.org/ticket/27794#comment:3>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list