71
edits
Changes
From Gramps
m
changed one line of thought.
# 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.cfg/ DistUtils2, developers only need to worry about is creating quality Python code. The rest Searching and adding files to Makefiles is no longer needed as it is handled dynamicallynow.
# 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.
