Re: Package Maker Problems
Re: Package Maker Problems
- Subject: Re: Package Maker Problems
- From: Stéphane Sudre <email@hidden>
- Date: Mon, 23 Jun 2003 13:57:12 +0200
On lundi, juin 23, 2003, at 10:15 Europe/Paris, Markus Hanauska wrote:
At the second where I select "Root Volume Only" flag, the installer
refuses the install the package anywhere. There are two HDs in this
Mac and it refuses to install it on the second HD saying that I can't
install it there, because I can only install it onto a volume with
MacOSX on it. But when the first one is selected, it says I can't
install it there either, without providing any reason, but (null) is
written behind the message in round brackets.
Now when I select the second HD and then jump back to the first one,
all of a sudden the exclamation mark becomes a green arrow and I can
install it there...?!? The same happens if I go back and then forward
again. Whenever I start installing the package, the root volume is
always pre-selected, but there's always the blue exclamation mark and
the text saying I can't install it there. Now when I go back one page
and then forward again or somehow deselect this volume and select it
again, it's a green arrow and the text says installation is okay. What
goes? And once it became a green arrow, I can install the package and
everything works perfectly fine!
But I can't release the package like that and then tell people "To
install it, you first have to go back one page and then forward again
to get the green arrow". Why can't I install it at once? What's wrong?
I have other packages that require installation to root volume as well
and they are working fine. And don't worry, the user has alread root
privileges at that point, because root authorization is required to
install the server and the StartUpItem (otherwise it wouldn't work
once the arrow turned green).
AFAIK, it's a bug in Package Maker 10.2 or in the Install framework.
And another annoying problem. In the end I have three packages.
Client, Server, StartUpItem. I'm trying to make a Meta Package,
consisting out of the three packages. I enter the description, drag
all the three single packages to the list and choose to create a
package. Package Maker says that everything went well, but the
resulting package is way too small (only a few KB, should be ten times
the size), the single packages can't be found inside and installation
fails with error 999 whatever that is. Any idea what could be wrong
here? I already added the single packages as "Resources" to the meta
package and then the packages were inside and the size was correct,
but I get the same error. However, I once was able to successfully
create a meta package that could be installed, too, but I don't know
what the difference was.
IMHO, it's not a good idea to use the Package Maker version shipped
with 10.2:
* It does not produce Installer that can be used on 10.1
* It introduced bugs.
* The documentation is worse than on the 10.1 version
You can limit the installation to a specific or specific volumes with
the 10.1 version using an undocumented feature (but since the whole
thing is not correctly documented, maybe "undocumented" is not the
appropriate adjective).
Namely, this undocumented feature is the 'VolumeCheck' file that you
can find in some Apple's packages. There's one in the most recent Apple
packages (to prevent installing a package on pre 10.2 system for
instance).
On the second problem:
Did you add the extension to the name of the sub-package in the list of
package names?
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.