Comment 10 for bug 475891

I took this fix line from line from Debian (see the bug report).

What the debian maintainer is doing is creating ~/.eagle which contains symlinks to all the "data" in /usr/share/eagle and contains a copy (not a symlink) of /usr/lib/eagle/bin/eagle.

His original package included the symlinks, but he didn't include the executable. He updated the package on Oct 19 to include the fix we have here.

I believe he does this because the binary (which is non-free and precompiled) expects to be run in the same folder as the data, but Debian policy doesn't let you put executable wrapper or bins inside /usr/share/ .

This is my guess from detective work looking at the package. There are probably other ways of doing it (I packaged something for Debian where I place all the binaries in /usr/bin and then wrote a wrapper which just cd into /usr/share/<package name> and then called the binaries from there), but this seems valid. He's an experienced DD, and I believe policy pushed him in this direction.