On Nov 30, 2005, at 11:53 AM, Frederick Cheung wrote:
On 30 Nov 2005, at 19:02, John Stiles wrote:
To summarize, wouldn't it be great if we could add our app to the
"Repair Permissions" check list? It seems like this could solve a
lot of problems for us. Unfortunately, I haven't got a clue as to
how this could be accomplished. I know it involves the files at /
Library/Receipts/, but these don't seem to be in a human-readable
format. I'm told that the Apple installer knows how to create
receipts, but we already have our own in-house installer
technology which gives us much more flexibility than Apple's
installer will allow us; switching to Apple's installer wholesale
is not an option.
Is anyone knowledgeable about Repair Permissions here? Is there
another list which I should ask on?
Thanks for your help :)
As I understand things, the packages that are in /Library/Receipts
are just normal packages, but with the archive that normally
contains the actual files to install (Archive.pax.gz) removed.
What you have left is a .bom file (bom = bill of materials?) which
is basically a list of everything the packaged installed, what the
permissions are etc. You can inspect a .bom with the lsbom
utility, create them with mkbom. I reckon would allow you to
create your own receipt.
Is mkbom going to be installed on a non-dev-tools machine?
In tiger it's in the Essentials package which is always installed. I
think it was in the BSD package before
Fred
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
