PackageMaker: requiring admin password when it should not

I've been seeing a really strange "anomoly" with a package I've created.

None of the files in the package are configured to require the Admin password and the install

destination is specified to be the user home directory. However, with the *same* .pkg file, I

see three different installations:

1) Everything goes along with minimal interaction and everything is installed where it

should be.

2) Almost the same, except the user is presented a window asking where to install the

package: the user directory or some other location.

3) With either of the two above, there may be a popup requesting the admin password. But

even with the correct password, the package files are not installed; even though the install

is declared successful. (I haven't been able to figure out where it thinks the files are going.)

So there are really two questions. First, why is the user ever queried about the destination

of the package files when the package is configured to use the home directory. Second,

why is the user promoted for the admin password.

As I said, this is with the same package file. Double clicking it will present one of the

scenarios above.

This certainly makes for a poor installation experience. I'm wondering it there is something

I've done (ore haven't done) which would cause these to happen.

Suggestions or comments welcome.

Oh yes, it makes no difference whether I use the PackageMaker GUI or the command line

interface.

- Mark