site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=jMeLy/yF35wNjLY3JlbCFHKsN1c5NtMLG2BhoZrdmew=; b=W8WIVN8CQmi47H7b0MQz1L3GEZm9e2WClD/w/cOQ/PUdTLMidY7yl9le49wymrVfu0 jVylnKuhSxvq93IX9qLtB5++6pjYerSUYg0P4/r/Nz9n7QGMo2rFZwXVOqbXyjyy1rLJ 5ztH+lKuNqZJt2WhvIyFJunU30oDjO4oN64YI= On Thu, Jul 14, 2011 at 11:15 PM, Neacsa Bogdan Valentin <neacsa_bogdan_valentin@yahoo.com> wrote: [...]

All the dependency_folders are in my package. Now I've started an apple discussion before this and from what I found from there is that all the instructions are run from the installers specific context. But what exactly does that mean ? To better formulate my question: if the PC that will install my package has python installed, will "python" as a command still be available in the installers context ? How can I get the path/location of this context ? Are there any simpler alternatives to packageMaker that could handle scripts like this better ?

You can call python from your post install script: - it's usually better to use absolute path for command line tools. i.e. /usr/bin/python - if what you are doing in your post install script is to call a python script, why not have the python script be the post install script? Regarding contexts, the extra resources of a package are extracted at the same level as your post install script. So ./ should work fine to get to the relative location. Or are you looking for another location? _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.a... This email sent to site_archiver@lists.apple.com