It's actually on both PPC and Intel, and it's from forgetting to update
gramps.accel after upgrading Gtk past 2.24.10, which changed the mapping
of alt/option from Mod5 to Mod1.
For gramps40 and master, the problem was masked by the bundler putting
the file in the wrong directory.
To data and images so that they're together with the other resources
instead of in site-package/gramps. Aside from a better source and
installation layout, this makes it easier to bundle them.
svn: r22577
Uses GRAMPS_RESOURCES to override the root location of the Gramps data
files (which would normally be $(prefix)/share). In setup.py install,
writes $(prefix)/share to gen/utils/resource-path, installs that file,
then deletes it again from the source tree. The presence or absence
determines whether Gramps is running from the source directory or from
an installation.
Const.py is now a static file; const.py.in is no longer used. Note that
because importing const into setup tried to initialize things that we
don't want initialized, VERSION is removed, and imported from
gramps.version -- a file which will be added in the next change.
Consequently, this commit will not run.
svn: r21618
NOTE: This uses the unstable modulesets which build the Gtk stack from the
current git masters. Builds may fail from time to time because of bad
commits. I'll fix this in a week or two after I've updated the stable
moduleset for Gnome 3.6.
svn: r20484
Make Arial Unicode MS the default face for OSX
Supports East Asian, Semitic, and European scripts, but not Indic
(Hindi, Telugu, Tamil, Thai, etc.). Since Pango's ATSUI backend doesn't
support fallback, users of these scripts will have to override the
default face in their ~/.gtkrc-2.0
svn: r18790
Importing gramps at the end of rungramps causes threading deadlocks because of a lock (held by the main thread as long as Gramps is running) on import.
svn: r17706
