Re: packagemaker blowing off custom icons now?
Re: packagemaker blowing off custom icons now?
- Subject: Re: packagemaker blowing off custom icons now?
- From: Stéphane Sudre <email@hidden>
- Date: Thu, 1 May 2008 14:24:10 +0200
On May 1, 2008, at 5:59 AM, Paul Cook wrote:
That was my experience as well.
Hopefully, others will read this post and avoid having to spend to
much time trying to figure it out on their own.
I suppose this is technically a but that we should all report.
Otherwise, unless someone from Apple actually monitors this list,
it won't get noticed and fixed.
It could be a duplicate of Problem ID 4350008 I filed in Nov 2005
which is still said to be opened. Since then I wrote an open source
version of SplitForks (http://s.sudre.free.fr/Software/Source/
Goldin.zip).
18-Nov-2005 02:51 PM Stephane Sudre:
I think there's another bug in SplitForks which may explain why some
things are not working properly.
Example:
--------
The "Dreamweaver 8" application (Trial evaluation) is a package and
the "Dreamweaver 8" folder has its kHasBundle flag set.
Let's copy "Dreamweaver 8" to "/tmp/501/testDreamWeaver/"
As far as I can tell, the correct result of a SplitForks operation
for the "Dreamweaver 8" folder shall be:
0000000 0005 1607 0002 0000 0000 0000 0000 0000
0000010 0000 0000 0000 0000 0002 0000 0009 0000
0000020 0032 0000 0020 0000 0002 0000 0052 0000
0000030 0000 0000 0000 0000 0000 2000 0000 0000
0000040 0000 0000 0000 0000 0000 0000 0000 0000
0000050 0000
0000052
i.e. Folder Info with kHasBundle 0x2000 set and an empty resource
fork. (According to the documentation in the Reference Library CD of
March 1999).
Now let's see the different results we get:
NB: current_dir is the current_working_directory when the command is
launched.
o SplitForks run by a tool launched by a Bootstrap context daemon:
current_dir: /
/Developer/Tools/SplitForks /tmp/501/testDreamWeaver
._Dreamweaver 8 (hexdump)
0000000 0005 1607 0002 0000 0000 0000 0000 0000
0000010 0000 0000 0000 0000 0002 0000 0009 0000
0000020 0032 0000 0020 0000 0002 0000 0052 e340
0000030 1000 0000 0000 0000 0000 2000 0000 0000
0000040 0000 0000 0000 0000 0000 0000 0000 0000
0000050 0000
0000052
=> Wrong. The resource fork length is said to be 0xe3401000, yet
there is NO resource fork.
-----
o SplitForks run from the Terminal:
current_dir: /
sudo /Developer/Tools/SplitForks /tmp/501/testDreamWeaver
._Dreamweaver 8
0000000 0005 1607 0002 0000 0000 0000 0000 0000
0000010 0000 0000 0000 0000 0002 0000 0009 0000
0000020 0032 0000 0020 0000 0002 0000 0052 e140
0000030 1000 0000 0000 0000 0000 2000 0000 0000
0000040 0000 0000 0000 0000 0000 0000 0000 0000
0000050 0000
=> Wrong. The resource fork length is said to be 0xe1401000, yet
there is NO resource fork.
current_dir: /tmp/501/testDreamWeaver
sudo /Developer/Tools/SplitForks Dreamweaver\ 8
._Dreamweaver 8
0000000 0005 1607 0002 0000 0000 0000 0000 0000
0000010 0000 0000 0000 0000 0002 0000 0009 0000
0000020 0032 0000 0020 0000 0002 0000 0052 0000
0000030 0000 0000 0000 0000 0000 2000 0000 0000
0000040 0000 0000 0000 0000 0000 0000 0000 0000
0000050 0000
0000052
=> Correct
current_dir: /tmp/501
sudo /Developer/Tools/SplitForks testDreamWeaver
._Dreamweaver 8
0000000 0005 1607 0002 0000 0000 0000 0000 0000
0000010 0000 0000 0000 0000 0002 0000 0009 0000
0000020 0032 0000 0020 0000 0002 0000 0052 e160
0000030 1000 0000 0000 0000 0000 2000 0000 0000
0000040 0000 0000 0000 0000 0000 0000 0000 0000
0000050 0000
0000052
=> Wrong. The resource fork length is said to be 0xe1601000, yet
there is NO resource fork.
--------------8<------------8<--------------8<------------
So I would tend to think that there's a bug in SplitForks. Probably a
bad initialized value for the length of the Entry.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden