• 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: Launching a ViseX installer from a PackageMaker installer
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Launching a ViseX installer from a PackageMaker installer


  • Subject: Re: Launching a ViseX installer from a PackageMaker installer
  • From: Scott Russell <email@hidden>
  • Date: Mon, 2 Apr 2007 09:35:13 -0400

Does the plugin's ViseX installer drop any remnants (akin to a PackageMaker receipt) anywhere?  Is there a config file left lying around with the plugin's installed directory saved as a value?  If so, you could query that file directly for the path.

Alternatively, could you include a "find" command in a preflight script to locate one of those audio samples and use its parent directory?

Best wishes,
Scott
-- 
Dr. Scott Russell

IT Support Engineer
Arts & Letters Computing, Distributed Support Services,
Office of Information Technologies, University of Notre Dame
Instructor of Horn, University of Notre Dame and Saint Mary's College
Assistant Horn, South Bend Symphony Orchestra

234 Decio Hall
574-631-7021
email@hidden
http://www.nd.edu/~srussel2/




On Apr 2, 2007, at 5:36 AM, Cormac Daly wrote:

At present, the best solution to our own requirements is a PackageMaker installer. The supplier of the plug-in I wish to install requires that I use a ViseX solution so unfortunately I can't integrate the two packages into one installer. I figure that calling the ViseX installer from the PackageMaker installer is the closest I'll get.

I won't go too deeply into specifics but I'll summarise the product as follows: my software is used for composing MIDI sequences in order to produce music. A 3rd party synthesiser (the plug-in) is used as the playback engine. The synth plug-in's installer must prompt the user to specify a directory where several GB of audio samples can be stored. My software's installer must then read this install location from the plug-in's plist file and store several of its own elements in the same directory - hence the need to run the ViseX installer first. 

 _______________________________________________
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: 
 >Re: Launching a ViseX installer from a PackageMaker installer (From: Luke Bellandi <email@hidden>)
 >Re: Launching a ViseX installer from a PackageMaker installer (From: Cormac Daly <email@hidden>)

  • Prev by Date: Re: Launching a ViseX installer from a PackageMaker installer
  • Next by Date: applescript and automount?
  • Previous by thread: Re: Launching a ViseX installer from a PackageMaker installer
  • Next by thread: applescript and automount?
  • Index(es):
    • Date
    • Thread