Comment 40 for bug 475891

The problem isn't with faulty binary in ~/.eagle/bin (see the above
debugging where we removed all copies of old binaries and it didn't
work, amongst other ideas), the problem is that the upstream
executable needs to have it's license key (this is a non-free program)
in the same directory as the binary. Neither I, nor the previous
maintainer know why it is, and why we can't just use exec -a or
symlinks to "trick" the binary, but that is the way it is (until
upstream responds to my prodding). The first time the binary is
executed, it will create the license key file. If the binary is in
/usr/bin, you need to exec the binary as root, and then you have a
.key file in /usr/bin, which isn't good either. The previous
maintainer came up with the current method of wrapping the original
eagle binary into a bash shell script with creates ~/.eagle and copies
the binary into it and symlinks all the data directories in
/usr/share/eagle-data/, then exec the binary in ~/.eagle/bin. The
license key is now owned by the user and located in the same directory
as the binary.

I contacted upstream and asked them to put command line arguments for
--datadir and --licensedir to avoid this mess. Right now, I'm really
looking for a solution to get this to work, because you are right -
all this copying is madness, I appreciate any ideas on how to clean
this up.