However I'll start to look at the OSX packager and I'll report
It's .pkg. This is a format with similar capabilities to .tgz, but it pops an install UI when clicked on the desktop. It's the file format used by OS X native installer app (like .msi on Windows). A .pkg is sometimes packaged in a .dmg for distribution. There exists also a console command to launch it. It supports launching pre/post scripts, too. This is not a "package manager" though, as it won't automatically do any such things as checking dependencies, counting references or use external repositories. It seems to support some sort of central database, but when I use 'pkgutil --packages' it will only list Apple ones (while I have some 3rd party ones for sure). There is no native UI or shell cmd to _uninstall_ installed packages either. Theoretically it supports installation to any dirs, not just the root, but I haven't seen such option in practice yet. It's most of the times used when vendor wants to install .kext, Frameworks or some other stuff in root / system dirs, or multiple dirs, besides the usual .app and other components otherwise easily installable by users themselves (f.e. .prefpanes). Overall in OSX .pkg is rarely used for desktop apps, and for these it's considered bad practice. To help removal of such packages, and to verify what they actually do, it's always possible to get a list of to be installed files. The command to create a .pkg is 'packagemaker'. This is the closest thing you can get on native OS X. [ Probably Harbour should support it over current .sh/.tgz solution. Personally I'm not interested though. ] Brgds, Viktor _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
