On 03/01/2013 19:31, Valerio Aimale wrote:
I've packaged it for Mountain Lion and x86_64. It should be
beta packaging. I've packaged from version 0.48+devel r12005
Please note that 0.48+devel r12005 is not a stable or new "version" -
it's the current unstable development branch (for 0.49). Your package
should be clearly labeled as (unstable) development snapshot build.
The stable release branch (on which the latest bug-fix release 0.48.4 is
based on), is here:
and the tarballs are hosted at sf.net
as well as at launchpad.net
If somebody want to try and report problems, I'd appreciate it
Unfortunately, your app doesn't run on OS X Lion (to be expected if
built with MacPorts using default config ), and I can't test it, nor
really comment on it since no details about the actual packaging have
If you could upload your changes to the packaging scripts as well as any
additional scripts (not sure how you packaged the python modules), this
would allow others (not using Mountain Lion yet) to test local packages...
You could for example push a new branch on launchpad.net
, similar to the
one for this blueprint:
Or - if you are not familiar with bzr and launchpad - you could file a
new bug report and attach a diff to the report.
I'll add some quick initial comments below, based on the currently
available information about your package:
The Mac Os X packaging infrastructure in the source tree is a bit
ancient. Things I've noticed:
- configure.ac uses syntax that is not conforming anymore with
autoconf/automake/authohear 1.13. Going forward that should be updated.
- Bug #1094576 <https://bugs.launchpad.net/inkscape/+bug/1094576>
“Patch for autogen.sh and configure.ac to support automake 1.13”
- the scripts osx-build.sh os-app.sh needs update for the newest
versions. they don't work out of the box.
Long-standing known issue ever since Snow Leopard was released (old src
requires SDK 10.4, among other things, uses deprecated features, not
ported to Cocoa, etc.).
I once tried to update it with minimal changes to make it at least build
on Lion (let alone work as expected), but the changes are likely to be
completely wrong (I don't know how to code in C/C++/Objective-C) ;)
- the dylib base relocation infrastructure needed to be rewritten
Not sure what issue you hit (some problems which made it fail for me had
been reported in bug #532765 “osx packaging: issues with fixlib() in
- the Platypus-derived ScriptExec executable might not be needed
Unless code is added to the binary inkscape itself (along with further
desktop integration), using a shell script as launcher will not support
any features of the dock and the native launch services - at least the
shell-launcher script from gtk-mac-bundler (gtk-osx) has these issues:
Bug #1045959 <https://bugs.launchpad.net/inkscape/+bug/1045959>
[inkscape-quartz] add DnD, 'Open with…' support for Dock & Finder icon
- in this version, the app bundle executes the sh script directly.
Do extensions which themselves call inkscape on the commandline (e.g.
restack, or dimensions), work with this kind of bundle structure and
- The version I packaged runs gtk-2.0+quartz. It does not need
X11/Xquartz anymore to run. This is the direction GIMP has gone to as well.
Which version of GTK+ 2.24 is included in the bundle? If the latest
2.24.14, does it include the patches from
Without those patches,
Inkscape and GIMP builds had been basically unusable for me (crash e.g.
whenever a text is highlighted in a text input box).
For me a major showstopper for releasing quartz-based packages of
Inkscape (at least based on the experience with my own builds on OS X
- Bug #1046068 <https://bugs.launchpad.net/inkscape/+bug/1046068>
“Inkscape (GTK+/Quartz) calls output extensions or crashes when
quitting while clipboard not empty“
which tends to make Inkscape crash on quit, whenever the clipboard had
been used in the current session.
Another annoying clipboard-related crash with the Quartz backend of GTK+
seems to be fixed if using GTK+ 2.24 with the latest patches from the
git branch (I haven't updated the bug report yet, because MacPorts only
recently included at least two of the required fixes into the gtk2 port):
- Bug #528632 <https://bugs.launchpad.net/inkscape/+bug/528632>
“GTK+/Quartz: crash in
- It uses the same theme as GIMP. I think it's a good consistency
decision, and it's the theme that looks best on Mtn Lion.
Adwaita GTK2 (from gnome-themes-standard 3.6.x) isn't bad either and
IMHO does integrate better with native OS X (at least on Lion),
including the look of the scrollbars. But that's a minor detail at this
 to quote Michael Wybrow on the same issue with Lion -> Snow Leopard:
I think it might be possible to build a package from Lion that runs
on older machines, but it requires that everything (all the macports
dependencies) be build against the Snow Leopard sdk instead of the
default Lion one. I had some problems trying this in the past and
just found it easier to use an older machine for the builds.