Difference between revisions of "GEPS 026: Replace 'make' for Gramps build"
Line 15: | Line 15: | ||
==Issues== | ==Issues== | ||
− | * PEP 345: Metadata for Python Software Packages 1.2 [http://www.python.org/dev/peps/pep- | + | * [http://www.python.org/dev/peps/pep-0345/ PEP 345]: Metadata for Python Software Packages 1.2 |
− | + | * [http://www.python.org/dev/peps/pep-0376/ PEP 376]: Database of Installed Python Distributions | |
− | + | * [http://www.python.org/dev/peps/pep-0386/ PEP 386]: Changing the version comparison module in Distutils | |
− | + | * [http://www.python.org/dev/peps/pep-0390/ PEP 390]: Static metadata for Distutils | |
[[Category:GEPS|D]] | [[Category:GEPS|D]] |
Revision as of 03:17, 6 April 2012
Move Gramps away from using Makefiles and to using setup.py and/or Distutils [1][2][3]2621
Purpose
- the core developers don't know Make, which was the case also in the past. Somebody of a company with expertise contributed the make system to Gramps.
- we need to update makefiles when adding changing files. With setup.py you only need to worry about changing directories, so simpler
- with make it happens from time to time that a new file is forgotten to be added in a release, causing 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 now
- we need less dependencies for installing gramps in linux. Already on windows makefiles are not used
- more and more projects that need make switch to cmake, ..., we should not stay with old technology just because it was already present