On Thu, May 06, 2004 at 02:28:26PM -0500, al wrote: > FWIW, OS X is effectively just a gussied up version of OpenBSD with the > Apple user interface lightly welded to it. Read: not exactly the same as > Linux, but pretty darn close. > > An OS X user needs an admin account to install software to the /Applications > folder (where OS X apps default install) but a user can install an app in > his/her home folder or sub-folders thereof. So far except for the > Applications folder, not too different from Linux. > > Some stuff may get installed to special folders in /Library, which is > generally readable by all users. Note that /usr, /bin, /sbin etc. all still > exist and can be used if the user has access... > > Point being that I'm not sure what the problems really are.
Well, I think first off it's that Tux Paint isn't so much an 'installer' as it is a program you download and double-click (all self-contained) on OS X, so there's no chance for it to create any global config files/etc. like you could with a Linux "make install" process, an RPM/DEB/etc package, or with the EXE NSIS-based(?) installer under Windows. And also, where and how Tux Paint looks for config files is Linux-centric, except when it's being built for other enviornments (e.g., "/etc/tuxpaint/tuxpaint.config" and then "~/.tuxpaintrc" are examined; unless you're on Windows, in which case it checks for ".\tuxpaint.cfg" or some-such) So a /little/ code adjustment is needed for Win and OSX systems, but I'm unfamiliar with the 'correct' way (the policy) of doing it in those environs. :) -bill! _______________________________________________ Tuxpaint-dev mailing list [EMAIL PROTECTED] http://tux4kids.net/mailman/listinfo/tuxpaint-dev
