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> |
||
|---|---|---|
| files | ||
| gfx | ||
| packaging | ||
| pyfpdb | ||
| regression-test | ||
| utils | ||
| agpl-3.0.txt | ||
| fdl-1.2.txt | ||
| gpl-2.0.txt | ||
| gpl-3.0.txt | ||
| Makefile | ||
| mit.txt | ||
| readme.txt | ||
| run_fpdb.bat | ||
| run_fpdb.py | ||
| setup.py | ||
| test_Python_Libs.py | ||
| test_Python.py | ||
Please visit http://fpdb.sourceforge.net for documentation, tips and help.