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=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=WOumx9wcHBYzWx5+AzyPoqZgBMJHA1SPvuJEBvCXsmI=; b=FepIgF2qKkN49C6Tr5Hz/zO/OU4xIT3erY0K2XFW8yLLErtjia25faML5rU+XCDWTm 9Kw5odu/YOwYNeVJVbJ3OveQwkH6/P0sl3hdzGw1DJvs6HBfy383fbrrVvoFrHywufh9 IFg9g9XNe+BMLYfeOtJF76rSob2MOhwtllMV8= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=CtLgRQk23f1EcAeSkRoIOJDqHYnpqAPTwf1TnU2SYFawYq9uWku+teWMEYqEXDH+JI skIs35zaIRGJhojBrPMi5cbwWQgvqhflvvOvDt3+n0okBi25+Y4aU4A1fK5cgAm4JvY4 GUaNxnbg0Olz+Qg9KkTFuMa1WaoP1M8DOCWdM= Hi folks, First off, much thanks to this list (via the archives) for already answering many questions. I have a few remaining questions about handling command-line utilities in an installer. Our (internal) package includes a cocoa applicaion, a kext, and several tools destined for /usr/local/bin. The command line tools are evolving quickly, and we are constantly adding new ones, which creates a maintenance load on the installer. We'd like to keep the installer fairly independent of the specific list of command line tools. Right now, our automated build builds everything, and copies all into /tmp/tools. The command line tools are archived into bintools.tar, and the installer package contains the app, kext and bintools.tar. When run, the installer installs bintools.tar into /tmp where a postinstall script extracts the contents into /usr/local/bin. Whenever we create a new tool, the packaging automatically gets it since it only handles the tar file and not individual files. Ideally, what I'd prefer is to remove the tar archive + script, and add the /tmp/tools/bintools/ directory to the pmdoc. Unfortunately, PackageMaker reads the contents of the bintools directory and adds those files explicitly to the pmdoc. Note that it adds the contents of the bintools directory as I am editing the pmdoc, not when the installer package is created. Conversely, Iceberg handles having a directory added to it in this way, and the contents of that directory are read when the installer package is built. Unfortunately, I can't use Iceberg in our environment. So: * What is the best practice for installing command line tools into /usr/local/bin? * Is there a way to Iceberg behavior out of PackageMaker w.r.t. a directory's contents? * How hacky is our current tar archive payload? Any problems doing this? thanks, -Brent _______________________________________________ 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