© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
Closing (obsolete):
1) The 'Script' dialog has been unhooked since Inkscape 0.47.
2) Conflicts with custom python installations:
Current (as well as future) Inkscape packages for Mac OS X (will) have rewritten loader paths of included dylibs, and no longer produce failures as originally described in this report (older packages relied on $DYLD_LIBRARY_PATH to load shared libraries from within the application bundle). Either methods has drawbacks though, and mixing binary libraries shipped with the application bundle with (likely) newer versions installed locally via MacPorts will inherently risk to run into binary incompatibilities (for details with regard to current packages (0.48.2), see also Michael's comments in bug #482993).
Future packages based on newer packaging scripts and GTK+/Quartz (currently work-in-progress, see mailing list) will make use of more advanced library path rewriting techniques (employing both "@executable_path and "@loader_path" for relative paths), which should allow included python modules like lxml, numpy and UniConvertor to import without error with either Python binary (system (Apple) or custom (MacPorts)).
Feel free to comment and reopen the report if you think that it was closed in error and that the same issues originally reported for Inkscape 0.46 in 2009 still apply to the current available package for Mac OS X (0.48.2), and the latest RC packages for 0.48.4 (see mailing list).