/usr/bin should normally be for programs used by the system during startup, if I understand correctly, and /usr/sbin for system programs used after /usr has been mounted. /usr/local/bin really ought to be the correct place for user scripts and programs.
I am not sure what the advantage of using an NSBundle over a script is. The location (/usr/bin in your suggestion) is important here, as long as it is in the path. Thanks for the answer. Carsten On 23/03/2008, Marcus <[EMAIL PROTECTED]> wrote: > > 23 mar 2008 kl. 00.01 skrev Carsten: > > > > The script installation in a more central place is an interesting > > thought. Is /usr/local/bin the Apple-sanctioned place for > > user-installed commandline utilities, rather than something like (the > > non-existent) /Users/<username>/bin? I could also install such a > > script alongside the .app bundle, which is a thought which had crossed > > my mind before I decided to ask more experienced Mac developers, but > > that might lead to path problems or long paths again, of course. > > > The problem with /usr/local/bin is that it does not exist on most Macs > and therefore you will also have to find out a way to put in in the > user's path. I think that most apps uses /usr/bin due to that reason. > > One alternative is to put it inside the application bundle and then > use a small Foundation tool inside /usr/bin and use NSBundle to figure > out during runtime where the bundle is stored. > > > Marcus _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
