But i don't think people realize that modifying a macports port for a custom install or test isn't any more difficult than a manual install. If an editor variable is defined all it takes is 'sudo port ed bibledit' and you change the version number and checksums, and the install the normal way. The next selfupdate wipes out local portfile changes so it is easy to revert.
So testing software versions is very manageable on a onsey-twosy basis anyway. It takes less skill to do this than a manual install IMHO
But it doesn't help here unfortunately. i forgot to mention that I'm still on 10.7 Lion so at least it isn't a 10.8 issue but probably that was already known.
Mark
.
>
Message: 2
Date: Fri, 12 Apr 2013 21:10:51 +0200
From: Teus Benschop <address@hidden>
To: address@hidden
Subject: Re: [be] Installing Bibledit on Mac OS X
Message-ID:
<CAFueZ4xdxX9SD+WwCMKfQ5E0pbMe+axkNm_mv7Ggr614ANXW=address@hidden>
Content-Type: text/plain; charset="utf-8"
Wish I had access to OS X in order to try a few things, like:
* After installing bibledit-gtk from source, then installing it through
macports, then running the bibledit-gtk version installed by macports,
would it still crash?
* It the macports version would run without crash, then removing the
version installed manually, would the crash be back again?
Teus.
?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nongnu.org/archive/html/bibledit-general/attachments/20130412/4da9e719/attachment.html>
------------------------------
_______________________________________________
Bibledit-general mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/bibledit-general
End of Bibledit-general Digest, Vol 55, Issue 8
***********************************************