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>
Changelog bump for new snapshot, and executable script renames that were
done for win32 setups.
(cherry picked from commit a5a507ece7)
Signed-off-by: steffen123 <steffen@schaumburger.info>
- updated copyright notices
- added copyright notices that were missing
- changed python to python2
- added gpl-2/3 license texts
- removed THANKS.txt file as the wiki version is more up to date
- removed empty fpdb_db.py
- added GPL2 to debian license file
Conflicts:
pyfpdb/Database.py
pyfpdb/DerivedStats.py
pyfpdb/SQL.py
pyfpdb/SummaryEverleaf.py
pyfpdb/TournamentTracker.py
pyfpdb/Tourney.py
run_fpdb.py
- updated copyright notices
- added copyright notices that were missing
- changed python to python2
- added gpl-2/3 license texts
- removed THANKS.txt file as the wiki version is more up to date
- removed empty fpdb_db.py
- added GPL2 to debian license file
* Deal with .pyw file extensions, because distutils doesn't
* Remove unnecessary win32-only build files from fpdb/*
* Tweak .desktop file for better menu integration
* Assume that build happens with python2.6
