Unlike Pavel's builds, it unzips as a complete installed OOo folder (so it doesn't fubar permissions on / and /Applications, but some of the folders aren't properly locked down like they are in 1.1.2 and other 1.9.xx builds).
Smokey _________________ "[...] whether the duck drinks hot chocolate or coffee is irrelevant." -- ovvldc and sardisson in the NeoWiki
Unlike Pavel's builds, it unzips as a complete installed OOo folder (so it doesn't fubar permissions on / and /Applications, but some of the folders aren't properly locked down like they are in 1.1.2 and other 1.9.xx builds).
but some of the folders aren't properly locked down like they are in 1.1.2 and other 1.9.xx builds
The 1.1.2 release has the /Applications/OpenOffice.org1.1.2 folder and all of its subdirectories are owned by root:admin (I recall seeing in the readme or somewhere else that this was done beginning in 1.1.x on all UNIX platforms for security reasons), whereas Maho's build ends up being owned by user_who_uncompresses_it:unknown. This perhaps not a big deal, but I thought I'd mention it (IIRC, the older 1.9.xx builds that installed in /opt were also locked down in this way).
jjmckenzie51 wrote:
Is there a torrent available for this program?
Not that I know of. I haven't made one because I'm on-and-offline atm.
Smokey _________________ "[...] whether the duck drinks hot chocolate or coffee is irrelevant." -- ovvldc and sardisson in the NeoWiki
The 1.1.2 release has the /Applications/OpenOffice.org1.1.2 folder and all of its subdirectories are owned by root:admin (I recall seeing in the readme or somewhere else that this was done beginning in 1.1.x on all UNIX platforms for security reasons), whereas Maho's build ends up being owned by user_who_uncompresses_it:unknown. This perhaps not a big deal, but I thought I'd mention it (IIRC, the older 1.9.xx builds that installed in /opt were also locked down in this way).
I was actually taught the exact opposite. You don't want to bring in an application as root:[anything] unless you completely trust the originator. Of course, this can make 'sharing' an application a bear, but there is alway sudo chown root * in the affected directory from a terminal session. This mainly applies to test software (which is what I do for a living and fun.) You do not want an untested application running as root and then have it run (whether by accident or deliberately) cd /; rm -rf -y *
If you don't know what that does, it is a basic delete everything and don't ask questions. This has appeared, in various forms, in code.
[quote="sardisson']
Not that I know of. I haven't made one because I'm on-and-offline atm.
Smokey[/quote]
Well, I'm really off the net right now, but I will be back in about two weeks. When I'm on the net, I use a dial-up type connection, which makes serving a torrent very hard, but I can still build on, using Trinity as the tracker.
I was actually taught the exact opposite. You don't want to bring in an application as root:[anything] unless you completely trust the originator.
IIUC, the folders and files are owned by root to prevent anyone/thing from mucking with them, but the app runs as whichever user launches it, not root (unless you happen to be silly enough to login is root).
Most of the apps that make up the "Core services" of Mac OS X are owned by root, but they run as me, e.g., when I decompress a zip archive using BOMArchiveHelper.
Smokey _________________ "[...] whether the duck drinks hot chocolate or coffee is irrelevant." -- ovvldc and sardisson in the NeoWiki
IIUC, the folders and files are owned by root to prevent anyone/thing from mucking with them, but the app runs as whichever user launches it, not root (unless you happen to be silly enough to login is root).
On other words, you need root permissions to change the app, and because Patrick blocked it, you cannot even run the app as root.
Sorry James, I think your point is a bit off. Though you can still have crappy installer mucking up your drive when given root permissions. _________________ "What do you think of Western Civilization?"
"I think it would be a good idea!"
- Mohandas Karamchand Gandhi
When running soffice, I get the grey window but impossible to open any document, the app crashs immediately !
Any idea, experience ?
You are not alone. It works for some people, and not for others. These are developer releases - use at your own risk, etc... The last version that sort of worked for me was 1.9m79.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You cannot download files in this forum
