• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: PackageMaker and custom folder icons
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: PackageMaker and custom folder icons


  • Subject: Re: PackageMaker and custom folder icons
  • From: Stéphane Sudre <email@hidden>
  • Date: Tue, 12 Feb 2002 17:56:37 +0100

Use a disk image. The first time a user starts the application, copy or
move the relevant items to /Library/Frameworks, /Library/StartupItems,
/Library/Preferences and /usr/bin. The user will need admin privileges to
do that anyway, and your application can take care of authenticating the
user and or insisting that the user is an administrator. Finally, don't copy
things to /Library/StartupItems or /usr/bin without a really good reason,
and ask the user for confirmation before doing it.

You're kidding?

If you need to copy files in /Library/StartupItems or /Library/Frameworks, the file ownership may need (read has) to be root:admin. The file permissions needing to be rw(x)rw(x)r-(x) or rw(x)r-(x)r-(x).

You can only do this in an application by using the Authentication Framework or using a s flagged binary (which is a bad idea).

The only utility of Disk Images is to prevent having problems when your final user is decompressing an archive containing file with name longer than the old Mac OS limit. I don't see the difference between having a .dmg file or a .tar.gz file on OS X.

And last killer point: egg and chicken problem.

A StartupItem is launched at Startup. If the StartupItem is not launched, the Application doesn't launch. So It's not possible to copy the StartupItem. And so on.

There are many UNIX
sites that will not or can not install anything in /usr/bin because it is
read-only and reserved for system components. That is why /usr/local/bin
and other directories exist.

Right.

Also consider if ~/Library/Frameworks, and
~/Library/Preferences are better choices. This approach has the added
advantage that if the installation is damaged (say because of an OS
re-install) then the next time the user runs the application, it can copy
its files again.

If you're installing an application on a machine using this, every user will have to install it and overwrite the Application in /Applications.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
  • Follow-Ups:
    • Re: PackageMaker and custom folder icons
      • From: "Erik M. Buck" <email@hidden>
References: 
 >Re: PackageMaker and custom folder icons (From: "Erik M. Buck" <email@hidden>)

  • Prev by Date: Re: How transparent window be implemented in MacOSX
  • Next by Date: Re: Cocoa, Pure java, or Carbon?
  • Previous by thread: Re: PackageMaker and custom folder icons
  • Next by thread: Re: PackageMaker and custom folder icons
  • Index(es):
    • Date
    • Thread