However, copying of framworks and libraries still fails, because under Lion /usr/bin/arch can give inaccurate information (i386 instead of x86_64), leading to the creation of a "i386" directory and the subsequent attempt to copy to a (non-existing) "x86_64" directory.
This is why I recommended returning $current_arch rather than "x86_64" from the architecture sub routine in pkgApp.pl. I agree, however, that this is a rather dirty fix.
A maybe better fix would be to use "uname -m" instead of "arch" for detecting the current architecture (this seems to return the correct architecture on Lion systems):
Okay, checked. The plugin depencies are okay.
However, copying of framworks and libraries still fails, because under Lion /usr/bin/arch can give inaccurate information (i386 instead of x86_64), leading to the creation of a "i386" directory and the subsequent attempt to copy to a (non-existing) "x86_64" directory.
This is why I recommended returning $current_arch rather than "x86_64" from the architecture sub routine in pkgApp.pl. I agree, however, that this is a rather dirty fix.
A maybe better fix would be to use "uname -m" instead of "arch" for detecting the current architecture (this seems to return the correct architecture on Lion systems):
Change pkgApp.pl, line 16 from:
my $current_arch = `/usr/bin/arch`;
to:
my $current_arch = `/usr/bin/uname -m`;