[Pythonmac-SIG] py2app trying to create a symlink that already exists

[Kevin Dangoor]

Following up to my own message. I just got back to looking at this
again this morning and managed to fix it. I don't have the full
answer, but thought I would post what I do know.

This morning, I spotted a couple of things.

1) the unnecessary bin directory was still in the Firebird.framework
on my Panther drive. I didn't run otool to see if any of those were
pointing at suspect things.

2) there was a copy of Firebird.framework already in the
build/bdist.... directory. Deleting that ultimately fixed the problem.
Creating an embedded Firebird on the Mac is a manual process right
now, so it's possible or even likely that the Firebird copy in there
was not in the final state.

The files in the Firebird.framework directory under build were not
symlinked in the same way as the ones in /Library/Firebird.framework.
So, py2app was copying over that one with real files, and then later
tried to copy from /Library/Firebird.framework which had symlinks in
place of some of those files. That's where it failed, because
copy_tree doesn't overwrite files with symlinks.

Kevin

On 8/12/05, Kevin Dangoor <dangoor at gmail.com> wrote:
> I'm using the embedded version of the Firebird database, and that is
> where the problem is coming in. I built Firebird myself on both Tiger
> and Panther. I've looked at /Library/Frameworks/Firebird.framework in
> both and they look the same. So, now to what the problem is...
> 
> Looking through py2app's output, the first framework copied is
> Firebird.framework, picked up as a dependency of kinterbasdb. As
> py2app continues copying stuff over, it eventually hits
> linking /Users/tazzzzz/projects/app/dist/myapp.app/Contents/Frameworks/Firebird.framework/Firebird
> -> Versions/Current/Firebird