On Apr 18, 2009, at 8:36 AM, Manfred Bergmann wrote:


Am 18.04.2009 um 12:34 schrieb DM Smith:

Regarding Mac, here is my experience (pretending to be a typical Mac user): 1) The installer was a surprise. I did not expect a pkg installer but rather I expected to have an app wrapped in a dmg that I would drag to the location of my choice. This is what both Bible Desktop and Mac Sword have. This kind of installer is not at all typical for a Mac user. I see it for things like MacOffice, Adobe Photoshop, EA games and other stuff from very well known vendors. It makes me wonder whether I want to install at all as it gives away root access to my machine, making me suspicious of a Trojan. Though I know you guys and am not suspicious, I am curious as to what is being installed that requires root access.

Surprise for me too. An installer is better than not having BibleTime on Mac at all.

IMHO a zip is better than a pkg installer and a simple dmg, better than a zip.


However installers are for more complex installations where you need to install Kernel extensions or need to run some post-install scripts. In this case, if all data is within the application bundle an installer is not needed.

The Admin access is to write the data into /usr where normally you don't have write access.
But the same applies to /Applications.

While it is true that /Applications needs Admin access, it does not require a password to drag an app there. It is reasonably safe as I know I am simply moving an app from the installer to /Applications.



5) Having found it I have know idea how to run it. Since I can't get to it in Finder, I can't execute it. From terminal one cannot run an app as the app is nothing more than a folder. No normal Mac user will ever use the Terminal to do anything. Not being a normal Mac user, I finally moved it /Applications where it can be seen by Spotlight, my preferred way of launching programs, and by Finder.

You can run application bundles from command line. Check out "open" command.
For example:
# open /usr/bibletime.app
should run it. But yes, normally very few people do this.

Thanks for the pointer!




Manfred


On Apr 18, 2009, at 3:03 AM, Eeli Kaikkonen wrote:

I forward this from bt-devel because some people here might be interested on Windows and Mac binaries (see 2) and 3) below) of BibleTime.


-------- Original Message --------
Subject: [bt-devel] CPack and other patches
Date: Sat, 18 Apr 2009 00:17:14 -0500
From: Greg Hellings <greg.helli...@gmail.com>
Reply-To: BibleTime development <bt-de...@crosswire.org>
To: BibleTime development <bt-de...@crosswire.org>

On http://www.crosswire.org/~ghellings/bibletime you should be able
now to find the following files:

1) Bt-with-Qt4.5.zip - a file which consists of all my BibleTime build
directories from Windows.  You can unzip it into, e.g.,
C:\Bt-with-Qt4.5 (where I had it), run CMake across the bibletime- svn and bibletime-build directories, then open Bibletime\Bibletime.sln and
things should build for you.  YMMV, but I'll try to help out as much
as possible.  You'll need your own build of Qt in order for this to
work.  Please let me know of problems you have, including if I'm
breaking GPL/LGPL licenses with it, but I think all the sources for
everything but Qt are included.  You'll still need to set a few
environment variables before running CMake: QTDIR needs to point to
the root of the Qt build you're using and BOOST_ROOT to the base of
the boost_1_38_0\ directory under this unpackaged folder.

2) bibletime-2.0.0alpha3-win32.exe - an installer, built with CPack,
that should install everything needed for users of BibleTime on
Windows.  Again, YMMV, but I've actually tested it, this time, on my
XP virtual machine and everything installs and runs. I'm not able to
get the SVG files running on XP, but there is a QtSvg4.dll and
QtSvgd4.dll in the 4.5.0 build -- getting those linked in properly (I modified CMakeLists.txt to link in the SVG libraries, but I they don't
seem to be used) might solve our issue of that display.

3) bibletime-2.0.0alpha3-Darwin.dmg - an installer I built, also with
CPack, as a first attempt at getting the system to operate as it is
supposed to. If someone with a non-development Mac could test it out
and give feedback, it'd be great to help me in figuring out exactly
what libraries are needed in the install pack.

4) CMake.diff -- a patch file that makes all the above possible.  It
includes the patches that make this possible and I've tested them on
both Windows and Macintosh.

Any feedback from others? We can certainly extend the CPack material
to cover other package systems.  It'd be nice to hear if I'm chasing
shadows or if this is a good direction for me to pursue.  I got no
feedback on the patch I posted here yesterday that dealt with all the issues except for the CPack. The patch in there now includes the one
from yesterday with a few fixes.

--Greg

--Greg

_______________________________________________
bt-devel mailing list
bt-de...@crosswire.org
http://www.crosswire.org/mailman/listinfo/bt-devel

_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page


_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page


_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page


_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page

Reply via email to