Previously the chmod setting *.pyw files executable was after prepgamesdirs, making the files world executable. It has been moved before it to allow prepgamesdirs
to do its job.
If fpdb is installed using an ebuild for the very first time then fperms mysteriously fails marking the *.pyw files as executables. During a second
install from the ebuild fperms was working which is more mysterious. I have found notices about this behaviour of fperms but couldn't find a proper
solution. However simply replacing fperms with chmod just does the work done.
Signed-off-by: steffen123 <steffen@schaumburger.info>
