Package Maker Problems
Package Maker Problems
- Subject: Package Maker Problems
- From: Markus Hanauska <email@hidden>
- Date: Mon, 23 Jun 2003 10:15:20 +0200
I need to make an install package, because the application consists out
of two parts and one part must be installed to a fixed location (the
user may not just move it somewhere else after installation); further
it's not stored in a "user friendly" location (it's below /usr , hidden
to many MacOSX users that are not familiar with UNIX). It will be a
StartUpItem, starting a process running in the background as some kind
of server.
The client part of it is a normal application package, that will be
installed to /Applications and that the user can move somewhere else if
he likes.
So far, so well. I created three packages with Package Maker. One for
the client, that works pretty well. It allowed user to customize
installation path during installation and installation of this package
works very well.
Then I created a server package and a StartUpItem package to install
the start up scripts (to be put into /Library/StartUpItems). The
location of these two should not be customizable. No problem so far.
But of course the user has to install these two packages on the root
volume *ONLY* and that's where my problem begins!
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).
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.
Any help is appreciated!
--
Best Regards,
Markus Hanauska
_______________________________________________
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.