Re: Installing command line tools
Re: Installing command line tools
- Subject: Re: Installing command line tools
- From: Brent Burton <email@hidden>
- Date: Sun, 8 Feb 2009 21:18:07 -0600
My schedule this past week made it very difficult to reply any sooner. Below..
On Thu, Feb 5, 2009 at 12:28 PM, Greg Neagle
<email@hidden> wrote:
>
> On Feb 3, 2009, at 9:36 PM, Brent Burton wrote:
>>
>> * How hacky is our current tar archive payload? Any problems doing this?
>
> It's a hack. As a system administrator, I want package receipts -
> specifically bom files, to tell what is installed. I don't want to have to
> read post-xxx scripts to figure out what other stuff got installed. We'll
> NEVER have a working uninstall capability as long as developers use post-XXX
> scripts to install stuff. Your bom would mention the tar archive (which no
> longer exists on the target) and neglect to mention the bin tools (which now
> are on the target). No uninstaller could ever make sense of this.
OK, this is a huge reason to not use a postinstall-based technique. I agree,
how else can a real uninstaller begin to work if we're hacking the process?
Last week I spent a fair bit of time looking into what works and what doesn't.
In short, PackageMaker mostly handles directories the way I desired. In
my original message in this thread, I said PM didn't expand directories at
all. As I've found, that's not true, but this doesn't mean that PM's expansion
of those directories is what is desired.
Basically, PM will indeed expand a directory when the package is built. The
limitation is that for any file that is expanded that was not listed
in the .pmdoc,
PM will use the filesystem's mode & ownership. As an example, if I create
a .pmdoc containing the directory "bin/" with one item "aaa" (root:wheel),
then at build time if the bin/ directory contains "aaa", "bbb" and "ccc", the
file information for aaa will be "root:wheel", but bbb and ccc will be
"localuser:staff". This is reasonable behavior, but is a bit too loose.
Thanks for posting the build snippet, Greg. I'm going to take a look
at that and a couple other ways.
-Brent
_______________________________________________
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