From: Tim L. <guy...@gm...> - 2010-03-28 17:10:55
|
I have now created the MacPorts Portfile for Gramps 3.2.0, and have asked for this to be uploaded to MacPorts. I would be very interested to know how many people are currently using Gramps on Macintosh, which version/port of Gramps they are using, which hardware architecture and which version of the Operating System they are using. I installed a fresh copy of MacPorts and built Gramps 3.2.0 from scratch. On my Mac OS X 10.4.11 iMac iSight (2.1 GHx PowerPC G5) this took 12 hours 53 minutes. I have tested the new MacPorts version in this environment. There were a few problems that have now been fixed in MacPorts. The remaining issues are: (1) If you had a previous installation of Gramps, you have to rename/ move aside /Applications/MacPorts when you do a fresh install. (2) MacPorts ticket 24127 (http://trac.macports.org/ticket/24127), libproxy 0.4.0 build failure - I loaded the portfile for 0.3.0 which worked OK. (3) The WriteCD plugin is unavailable. This relies on GNOME and has not been made to work on OS X. (4) The spelling checker is not installed because there is no MacPort of the python bindings to gtkspell, this results in the warning: "14484: WARNING: Spell.py: line 66: Spelling checker is not installed". (5) A warning message is produced: "Xlib: extension "RANDR" missing on display ":0.0"." According to the MacPorts FAQ (http:// trac.macports.org/wiki/FAQ#randr) "It's harmless and you should ignore it". (6)The Geographic View is not available because webkit-gtk does not build under MacPorts (MacPorts ticket 23464 http://trac.macports.org/ ticket/23464 and webkitgtk bug https://bugs.webkit.org/show_bug.cgi? id=36088). (7) When going into the file chooser (for example on export or import or plugin manager, you may get the warning: "GtkWarning: Unable to find default local directory monitor type". This doen't seem to be very serious, and seems to be a "more general gtk issue". See http:// www.mail-archive.com/bug...@gn.../msg03464.html. If you start gramps from the xterm window, don't forget to follow the instructions about setting paths for the X11 environment in http:// trac.macports.org/wiki/InstallingMacPorts. Instructions for installing the MacPorts version of Gramps are in the Wiki at http://www.gramps-project.org/wiki/index.php? title=Mac_OS_X_MacPorts. The latest version of MacPorts Gramps prior to this is 3.0.4. The latest official stable fink version is 1.0.10 for Mac OS X 10.4. The latest official unstable fink version is 3.0.4 for Mac OS X 10.5. The latest prebuilt binary version (http://www.gramps-project.org/ apple) is 3.1.2 for Intel and PPC, but this does not work on Mac OS X 10.4 PPC. Regards, Tim Lyons. |
From: Tim L. <guy...@gm...> - 2010-03-29 10:17:17
|
On 29 Mar 2010, at 06:17, Ryan Schmidt wrote: > > On Mar 28, 2010, at 12:10, Tim Lyons wrote: > >> (1) If you had a previous installation of Gramps, you have to >> rename/move aside /Applications/MacPorts when you do a fresh install. > > Why was this necessary? At most, you should have to "sudo port > deactivate gramps" to move the old one aside, then "sudo port > install gramps" to install the new one; I would never expect the > user to need to manually fiddle with anything in /Applications/ > MacPorts. Ideally, deactivating the old version would not be > necessary either, but I did not test upgrading. > "Fresh install" is probably not a precise enough description of what I meant. I deleted /opt to ensure that I had a really fresh start, then installed a fresh copy of MacPorts. When Macports ran, it found the / Applications/MacPorts directory and reported that this was unexpected because it had no record of it, and then failed with the message: Error: Target org.macports.activate returned: Image error: / Applications/MacPorts/Python 2.6/Build Applet.app/Contents/Info.plist already exists and does not belong to a registered port. Unable to activate port python26. Prior to this, I had tried upgrading, but got into a real mess for reasons that you don't want to know about. Anyway, I thought starting from a fresh copy of MacPorts would be a good idea because (1) I probably had lots of components that were no longer needed by Gramps, and I didn't want to keep upgrading them forever. (2) Wouldn't starting from a fresh be the only way to really check that the dependencies were correct. When I first started using MacPorts way back in March 2008, I seem to remember that some of the dependencies in some components were not quite right, and you needed to build something explicitly before building something else. I am happy to say that when I did the complete build, I had absolutely no problems whatsoever! > >> (2) MacPorts ticket 24127 (http://trac.macports.org/ticket/24127), >> libproxy 0.4.0 build failure - I loaded the portfile for 0.3.0 >> which worked OK. > > I fixed this. > Thanks, but I see that the new libproxy still doesn't work on Tiger, which is where I am at the moment! (Ryan has reported this on libproxy ticket 104) > >> (4) The spelling checker is not installed because there is no >> MacPort of the python bindings to gtkspell, this results in the >> warning: "14484: WARNING: Spell.py: line 66: Spelling checker is >> not installed". > > I'm not familiar with gramps, but a quick check (new family > history, new person, notes field) showed on-the-fly spell checking > working already, on Snow Leopard. This is after upgrading gramps to > use python 2.6. With python 2.5 I was seeing that warning too; with > 2.6 not anymore, so maybe using 2.6 has somehow automatically fixed > this. (Or maybe I've got some py26 module installed that's helping > here.) > I think the problem is the python binding to gtkspell (actually gtkspell2). I think that gnome-python-extras is only building the python module for gtkspell if gtkspell is present when gnome-python- extras is built. I.e. it all depends of the order of building. I have had spell checking working for me before, but not now. I have raised a ticket against this. http://trac.macports.org/ticket/24266. |
From: Stefan H. <my...@st...> - 2010-03-29 20:02:21
|
Hi Tom, thanks for your effort doing this. I used to work with version 3.1 on my Mac mini. But I recently decided to switch Mac FamilyTree and here's the reason why: As I'm using cross-platform environments I have to export and import / create new tree all the time when I sync the data back from Linux to Mac version. So there's no reason for me to keep it up, when I can do the same with clean mac os developed software using standard ged-file export and import. BTW: I was able to sync the data using unison from Mac to Linux without any problem but not back for the known reasons. Regards, Stefan Am 28.03.2010 um 19:10 schrieb Tim Lyons: > I have now created the MacPorts Portfile for Gramps 3.2.0, and have asked for this to be uploaded to MacPorts. > > I would be very interested to know how many people are currently using Gramps on Macintosh, which version/port of Gramps they are using, which hardware architecture and which version of the Operating System they are using. > > > I installed a fresh copy of MacPorts and built Gramps 3.2.0 from scratch. On my Mac OS X 10.4.11 iMac iSight (2.1 GHx PowerPC G5) this took 12 hours 53 minutes. I have tested the new MacPorts version in this environment. > > > > There were a few problems that have now been fixed in MacPorts. The remaining issues are: > > (1) If you had a previous installation of Gramps, you have to rename/move aside /Applications/MacPorts when you do a fresh install. > > (2) MacPorts ticket 24127 (http://trac.macports.org/ticket/24127), libproxy 0.4.0 build failure - I loaded the portfile for 0.3.0 which worked OK. > > (3) The WriteCD plugin is unavailable. This relies on GNOME and has not been made to work on OS X. > > (4) The spelling checker is not installed because there is no MacPort of the python bindings to gtkspell, this results in the warning: "14484: WARNING: Spell.py: line 66: Spelling checker is not installed". > > (5) A warning message is produced: "Xlib: extension "RANDR" missing on display ":0.0"." According to the MacPorts FAQ (http://trac.macports.org/wiki/FAQ#randr) "It's harmless and you should ignore it". > > (6)The Geographic View is not available because webkit-gtk does not build under MacPorts (MacPorts ticket 23464 http://trac.macports.org/ticket/23464 and webkitgtk bug https://bugs.webkit.org/show_bug.cgi?id=36088). > > (7) When going into the file chooser (for example on export or import or plugin manager, you may get the warning: "GtkWarning: Unable to find default local directory monitor type". This doen't seem to be very serious, and seems to be a "more general gtk issue". See http://www.mail-archive.com/bug...@gn.../msg03464.html. > > > > If you start gramps from the xterm window, don't forget to follow the instructions about setting paths for the X11 environment in http://trac.macports.org/wiki/InstallingMacPorts. > > > Instructions for installing the MacPorts version of Gramps are in the Wiki at http://www.gramps-project.org/wiki/index.php?title=Mac_OS_X_MacPorts. > > The latest version of MacPorts Gramps prior to this is 3.0.4. > The latest official stable fink version is 1.0.10 for Mac OS X 10.4. The latest official unstable fink version is > 3.0.4 for Mac OS X 10.5. > The latest prebuilt binary version (http://www.gramps-project.org/apple) is 3.1.2 for Intel and PPC, but this does not work on Mac OS X 10.4 PPC. > > Regards, > Tim Lyons. > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev_______________________________________________ > Gramps-users mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-users |