Regarding Application Support/Sword vs Eloquent: it is a simple change to JSword to add another place where modules are stored. The trick would be for SWORD to look in more than one place.
In Him, DM Cent from my fone so theer mite be tipos. ;) On Jan 29, 2011, at 4:02 AM, Manfred Bergmann <manfred.bergm...@me.com> wrote: > Hi Guys. > > I think it is relatively unlikely to succeed putting MacSword/Eloquent in the > Mac AppStore. > The main stumbling blocks are: > > - the module installer: > Apple doesn't allow "Apps that download or install additional code or > resources to add functionality or change their primary purpose will be > rejected" > > - creating the links for the module utilities in /usr/local/bin. For that we > aquire admin priviledges via an Apple API but allow doesn't allow that either: > "Apps that request escalation to root privileges or use setuid attributes > will be rejected" > > - finally Apps are only allowed to create folders in the filesystem that > reflect the name of the App. We create a "Sword" folder where the modules are > stored. > Apple says we do not "comply with the Mac OS X File System documentation". > > > Nic, did you have similar issues (module installer and filesystem)? > > I'm not willing to remove this from the App and If Apple doesn't except > explanations for those then AppStore is a "no go". > > > > > Manfred > > _______________________________________________ > 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
