• 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: changing destination path
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: changing destination path


  • Subject: RE: changing destination path
  • From: "Glover,David" <email@hidden>
  • Date: Thu, 18 Jun 2009 16:31:49 +0100
  • Thread-topic: changing destination path

If you build your package to target Leopard only, it builds what it calls a ‘flat-package’ which doesn’t appear as a bundle.

 

If you target Tiger and later, then it creates a package as a bundle, and you can create a Plugins folder within the Contents folder, and add the .bundle and .plist into there.

 

Dave

 

From: installer-dev-bounces+david.glover=email@hidden [mailto:installer-dev-bounces+david.glover=email@hidden] On Behalf Of Mike Erickson
Sent: 18 June 2009 15:51
To: email@hidden
Subject: changing destination path

 

We want to use packagemaker to install a plugin into Photoshop. A plugin consists of one or two binaries, some help files and some settings files. Photoshop requires that these files be in very specific places so it can find and load them.

 

If the user has more than one version of Photoshop installed, we allow them to choose which version to install into.

 

It is very problematic to allow the user to simply choose the proper folder in the proper version of Photoshop via a finder panel. We need to find Photoshop and the proper directory for them, and use that folder as the installation destination. The tech support would be nightmarish if we didn’t, believe me.

 

I have downloaded and examined the Sample for an installer plugin. In the readme, it says to look into the contents of the pkg file and create a folder called ‘plugins’. Unfortunately, with packagemaker 3.0.2, the generated pkg file does not appear to be a bundle.

 

Can you still use installer plugins with the newer versions of packagemaker? If so, how?

 

We used to do this with Vise X from MindVision. Don’t get me started on that product. Suffice it to say, we *really* want to go to packagemaker!

Promethean Limited is a company registered in England and Wales with company number 1308938 and VAT number GB 572 2599 18


Promethean Ltd and or associated and or subsidiary companies :

The views expressed in this communication may not necessarily be the views held by Promethean Ltd and or associated and or subsidiary companies.

This e-mail is for the exclusive use of the addressee(s). Unauthorised disclosure, copying or distribution is prohibited.

This e-mail message has been swept for the presence of computer viruses.

Promethean Ltd and or associated and or subsidiary companies accepts no liability for any loss resulting from this email transmission

Promethean, Promethean House, Lower Philips Road, Blackburn, Lancashire, BB1 5TH, UK.

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >changing destination path (From: "Mike Erickson" <email@hidden>)

  • Prev by Date: changing destination path
  • Next by Date: Finding installed applications by bundle ID in PackageMaker 3.0.3
  • Previous by thread: changing destination path
  • Next by thread: Finding installed applications by bundle ID in PackageMaker 3.0.3
  • Index(es):
    • Date
    • Thread