Re: [OT] How to extract a BOM archive correctly?
Re: [OT] How to extract a BOM archive correctly?
- Subject: Re: [OT] How to extract a BOM archive correctly?
- From: Eduard de Jong <email@hidden>
- Date: Sat, 6 Oct 2007 22:49:49 +0100
You are right, the man pages are very thin on actual data on the
format of the file.
The way to make a bom file, which they suggest is to create a
directory structure with all names, owner id, group id and acsess
bits set and then feed that into mkbom. As i understand it, none of
these files need to be present with actual data to make a bom.
One aproach could be to use a shell script to parse the output of
lsbom to reconstruct the file system is specifies with empty files,
apply your modifications to the result and then get a modified bom
with mkbom.
At 01:54 +0100 06-10-2007, Finlay Dobbie wrote:
On 05/10/2007, Karan, Cem (Civ, ARL/CISD) <email@hidden> wrote:
I've read the man pages before, but they aren't specifications; that is,
if I write a tool that is designed to parse a BOM file, I need to know
what the different bytes are that it sees. I can reverse engineer this,
but that can lead to errors that I would prefer to avoid. The man pages
for bom, lsbom, and mkbom (at least on my machine, a fairly stock
10.4.10 machine) don't give enough information on this for me to write a
tool. Basically, I'm looking for a spec like you'd find if you were
trying to create a new jpeg library; you need more than what help files
for your favorite jpeg viewer provide. In the same way, I need more
than what the man/info pages provide.
There is no such specification, it is a private file format. You could
always just parse the output of lsbom, which will give you what you
need.
-- Finlay
--
Eduard
"E por se movo"
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden