PackageMaker ignores install files
PackageMaker ignores install files
- Subject: PackageMaker ignores install files
- From: Sunrise Ltd <email@hidden>
- Date: Tue, 20 Jul 2004 17:46:55 +0900 (JST)
I have built an install package with PackageMaker. This is
for a Unix utility that just so happens to need files
installed into /usr/sbin.
PackageMaker picks those files up and puts them into the
Archive.pax.gz file, so far so good. However, it does not
include them in the Archive.bom bills of materials file.
As a result, the installer simply ignores those files and
they don't get installed. There are several other similar
instances where files are being ignored in this way or
where they don't even show up in the Archive.pax.gz file
either.
Yet PackageMaker displays a success window telling me that
"the package was created without any problems". Also, I
couldn't find any reference that said it didn't support
certain files or locations.
Am I missing something here or is this a known bug?
I know that I can install into other locations, ie /tmp
and then move them into their proper locations with a
postinstall script, but what is the point of PackageMaker
if I have to code my own installer after all?
Also, since there seems to be no documentation that lists
DO's and DONT's, and PackageMaker always giving success
feedback without any warnings or errors, one has to waste
a lot of time to verify the contents of Archive.pax.gz and
Archive.bom everytime.
This is not what I expect of a company that spares no
opportunity to pride itself for excellence and attention
to detail. This PackageMaker thing would seem to be the
kind of tool you'd expect from a five year old with an
attention span of 15 minutes. Shame on Apple for releasing
it in this preliminary state.
So, my question is this: What do other folks do in cases
where you need to install stuff into the BSD layer? Do you
simply clean up Apple's mess with postinstall scripts or
is there a fix? Also, how do you know when you can trust
PackageMaker? Do you always go through your Archive.pax
and Archive.bom files to check? Is there a tool that does
this automatically?
Any feedback appreciated. Also any other problem reports
about PackageMaker are welcome. For if there is no fix for
this mess, I am tempted to write a fixup tool myself, call
it something like "Apple's PackageMaker Sucks" and release
it so other developers new to the platform don't get hit
by this mess.
Sorry for the ranting but I am really not amused by this
and I believe that people who are always bragging how much
better they are than anybody else deserve being kicked in
the butt much harder than anybody else when they screw up.
thx
benjk
http://bb.yahoo.co.jp/
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.