71
edits
Changes
From Gramps
m
Word changes and some substitution of setup.cfg and DistUtils2.
# The core Gramps developers do not know [http://www.gnu.org/software/make/ GNU Make], which was the case also in the past. Somebody of a company with expertise contributed the make system to Gramps. ([http://gramps.1791082.n4.nabble.com/prepare-gramps-3-4-tp4329757p4613312.html Actually, I'm pretty fluent with autotools. John Ralls])
# With GNU Make developers need to update makefiles when adding and changing files.<br />*With setup.py cfg/ DistUtils2, developers only need to worry about changing directories; this is simpler to maintaincreating quality Python code. The rest is handled dynamically.
# With GNU Make from time to time it happens that a new file is forgotten to be added in a release, causing maintainance overhead for the release manager.
# Gramps is pure python, we don't need a makefile system checking for a lot of things it is checking for now.
# We need less dependencies for installing Gramps in linux.<br />*''Already on windows makefiles are not used.''
# An increasing number of projects that need GNU Make switch to [http://www.cmake.org/ CMake], ..., we should not stay with old technology just because it was already present
