Re: More on Install progress messages
Re: More on Install progress messages
- Subject: Re: More on Install progress messages
- From: Kevin Brock <email@hidden>
- Date: Sun, 26 Jul 2009 21:31:41 -0700
On Jul 25, 2009, at 3:00 AM, Iceberg-Dev wrote:
I'm a bit surprised by the part related to the inability to rename a package based on its payload. There should be no relation at all between the payload and the name of the package.
Well, the auto-generated package name appears to be *derived* from the payload. Note that I'm not talking about the package ID, which I can change at will, but about the name of the actual package inside of the flat package. The directory name 'foo.pkg' that you see when you expand the package. That has no relationship to the package ID. Some renames were fine. It was just non-bundle items that weren't. The documentation says that the value in the Distribution file is a URL, and can even point to remote files.
Regarding the lack of support for spaces, apparently when you have a package name with spaces, they are removed by PackageMaker.
It displayed the correct (with spaces) filename in the install log file, so it *looked* like it was finding them. It clearly doesn't support them though. I wonder--does that mean that if you specify a remote URL for the package file that it can't have in the URL or it won't work? Or is this a special lack for internal packages? I'll have to play with that a bit and see what happens.
If I were you, I would not go for one package for each component of the application/solution. I don't see the point in doing this (and in having implemented this in PackageMaker). Apple does not do that for its own packages so I don't understand why they are enforcing this. If your kext is updated, your application would probably be updated to reflect at least the new minor version. If your daemon is updated, idem.
Not completely true in this case. One part of the product is quite likely to be updated independently of the rest. It's possible that installs for a separate product might upgrade one of the packages... Some of that is still being worked out. What's being packaged here is a product with two different pieces, each of which contains multiple components, where each of the two pieces can be updated somewhat independently.
With PackageMaker, it might be worth re-creating the branches of the '/' hierarchy you need and then uses this fake '/' folder as the root of your package payload.
I tried that pretty early, and have tried again recently. PackageMaker crashes on build when I try this with our set of components. No clear clues in the log about why--just *boom*. I'm going to be filing a bug about that. I do have some data that got dumped out when it crashed that I'll be sending Apple. We've got a moderately complex project, but nothing that should crash PackageMaker that way. Some KEXTs, a couple of daemons, an application & a few scripts/plists. Nothing too weird about the directory tree. Done as multiple items, each with an install location, things work smoothly. Just can't rename some of the packages.
Kevin
|
_______________________________________________
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