• 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: Additional info needed about "PackageMaker"
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Additional info needed about "PackageMaker"


  • Subject: Re: Additional info needed about "PackageMaker"
  • From: Dan Wood <email@hidden>
  • Date: Tue, 09 Oct 2001 16:23:40 -0700

A couple of thoughts, to see if there's a way to avoid PackageMaker (which I think Apple is trying not to document so that others won't use it) -- first, I think you want to put your extensions in /Library/Extensions, not /System/Library/Extensions. /System is for Apple only, and the way that domains work is that multiple domains are supposed to be searched. See my article in the latest MacTech.

Also, one thing that some Apple engineers suggested to me at WWDC and also what I've heard on the list is that you could have these pieces bundled in your application, and when it first starts up, it copies the resources over to their destination. Presto! No installer.

Of course, there may be some other reason why you can't do it that way, but it makes sense to see if you can get away with a simpler approach before going down the installer path....

Dan Wood


On Tuesday, October 9, 2001, at 03:54 PM, Nicolas Robin wrote:

I wish we could do just drag-and-drop, but unfortunately their environment
is not as simple.

For example, we need to install some pieces of software, like a driver in
the "/System/Library/Extensions" folder and an other one in the
"/Library/StartupItems" folder...

We also need to do some upgrades where some files will be updated and some
others won't.

There are also some cases where there is a need to install some aliases at
some specific locations of the hard disk...

I guess the question now is: Does Apple plan to have a serious and complete
documentation of "PackageMaker" one day ? Do they want the developers to use
that tool to make the greatest installers on OSX or do they want to keep
this tool for themselves and let the "outside world" use other tools like
Aladdin's InstallerMaker or Mindvision's Installer Vise ?

Nicolas.

From: Finlay Dobbie <email@hidden>
Date: Tue, 9 Oct 2001 21:46:25 +0100
To: Nicolas Robin <email@hidden>
Cc: <email@hidden>
Subject: Re: Additional info needed about "PackageMaker"


On Tuesday, October 9, 2001, at 09:38 pm, Nicolas Robin wrote:

The company I work for, is at a stage they would like to have an
installer
for all their recently carbonized applications.

Why exactly do they need an installer? Can't they just have
drag-and-drop, the preferred installation method on OS X?

-- Finlay
_______________________________________________
cocoa-dev mailing list
email@hidden
http://www.lists.apple.com/mailman/listinfo/cocoa-dev



--
Dan Wood
email@hidden
http://www.karelia.com/
http://www.bikealameda.org/
Mac OS X Developer: Online Resume: http://www.karelia.com/resume.html


References: 
 >Re: Additional info needed about "PackageMaker" (From: Nicolas Robin <email@hidden>)

  • Prev by Date: Re: Additional info needed about "PackageMaker"
  • Next by Date: Re: Persistance
  • Previous by thread: Re: Additional info needed about "PackageMaker"
  • Next by thread: Re: Additional info needed about "PackageMaker"
  • Index(es):
    • Date
    • Thread