• 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: Installing command line tools
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Installing command line tools


  • Subject: Re: Installing command line tools
  • From: Eli Bach <email@hidden>
  • Date: Tue, 3 Feb 2009 23:56:11 -0800

Brent,

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?

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?

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.


* Is there a way to Iceberg behavior out of PackageMaker w.r.t. a
directory's contents?

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...)


Eli

_______________________________________________
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: 
 >Installing command line tools (From: Brent Burton <email@hidden>)

  • Prev by Date: Installing command line tools
  • Next by Date: Re: Installing command line tools
  • Previous by thread: Installing command line tools
  • Next by thread: Re: Installing command line tools
  • Index(es):
    • Date
    • Thread