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:received:received:message-id:from:to :in-reply-to:content-type:content-transfer-encoding:subject :mime-version:date:references:x-mailer; bh=2QUKvtNtVxaqB+WM1Y5nm6tVMP/BeCPzEAAgKGSdKG8=; b=k8Jke7VL2QfixiqNt5sBAD/BoKQRaoqblh3kzolud4TF5/5NGzosrkND2L0jV+3Ut2 jTaO8NHovN9SHANPDydek1XKk4wtPl34HkWxha8gqv9WT25v7nFkufYiCBnfxJkspBCS QWPpWMx4JrHeZrDQpbg4V/dv667Of9jcbehM4= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:in-reply-to:content-type :content-transfer-encoding:subject:mime-version:date:references :x-mailer; b=F3SLpr6oOoqcIUr37cW2aGU7zcvnfeCQ4uQm8t/6RS8LHihfHFVgRpIrTv1sricchy aEut0nIPRTqJ/SivCltDzcsQWaL4jRaNUfQckdPKua1hXoGVgFapK/MYL09EBiC/brRB sXts7036pcIseKzyEVHf+capHYttHxPG3GBeQ= Brent, On Feb 3, 2009, at 9:36 PM, Brent Burton wrote: 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? Eli _______________________________________________ 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... First, I would say, you've got a system that works, it seems to not be a big problem for your users, so unless you have a specific problem or new tool that requires some special handling, why change it? I think it's a tossup between using an installer or you can do what BBEdit does, in that the tools are bundled into the app, and when the app is launched, it checks the installed version of each tool, and if any are out of date (or not present), it asks the user if they want to install the tools, and then goes through Authorization Services to install the tools in /usr/bin (but /usr/local/bin is also OK). You could update this process to get the tools from an internal server via http or whatever instead of needing the user to get a new application if only the tools have changed. Yeah, this behaviour annoys me as well (that you can't just tell it to grab everything in a folder when it builds, instead of just the files present when the folder is added to the package in PackageMaker). Offhand, I can only think of brute-forcing it in, as in, directly editing the plist's within the pmdoc (as it's just a folder of a couple of plists) * How hacky is our current tar archive payload? Any problems doing this? It sounds like a good, straightforward workaround for how PackageMaker currently works. I believe it was, and may still be, the kind of thing you had to do to install files into the current user's folder (I recall it being standard practice to install into /tmp, then move the files to the user's folder in a postinstall script, but the current version of PackageMaker/Installer may no longer need to do this...) This email sent to site_archiver@lists.apple.com