Difference between revisions of "GEPS 026: Replace 'make' for Gramps build"

From Gramps
Jump to: navigation, search
(Add bugs section)
Line 18: Line 18:
 
* [http://www.python.org/dev/peps/pep-0386/ PEP 386]: Changing the version comparison module in Distutils
 
* [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
 
* [http://www.python.org/dev/peps/pep-0390/ PEP 390]: Static metadata for Distutils
 +
 +
==Bugs==
 +
 +
* [http://bugs.python.org/issue5302 5302]: Allow package_data specs/globs to match directories
 +
* [http://bugs.python.org/issue8501 8501]: --dry-run option doesn't work
 +
* [http://bugs.python.org/issue12830 12830]: --install-data doesn't effect resources destination
 +
* [http://bugs.python.org/issue12393 12393]: Packaging should provide support for extensible categories
 +
* [http://bugs.python.org/issue14549 14549]: Recursive inclusion of packages
  
 
[[Category:GEPS|D]]
 
[[Category:GEPS|D]]

Revision as of 15:57, 13 April 2012

Move Gramps away from using Makefiles and change to using Pythons setup.py and/or Distutils [1][2][3]2621

Purpose

  1. The core Gramps developers do not know GNU Make, which was the case also in the past. Somebody of a company with expertise contributed the make system to Gramps.
  2. With GNU Make developers need to update makefiles when adding and changing files.
    *With setup.py developers only need to worry about changing directories; this is simpler to maintain.
  3. 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.
  4. Gramps is pure python, we don't need a makefile system checking for a lot of things it is checking now.
  5. We need less dependencies for installing Gramps in linux.
    *Already on windows makefiles are not used.
  6. An increasing number of projects that need GNU Make switch to CMake, ..., we should not stay with old technology just because it was already present

Issues

  • PEP 345: Metadata for Python Software Packages 1.2
  • PEP 376: Database of Installed Python Distributions
  • PEP 386: Changing the version comparison module in Distutils
  • PEP 390: Static metadata for Distutils

Bugs

  • 5302: Allow package_data specs/globs to match directories
  • 8501: --dry-run option doesn't work
  • 12830: --install-data doesn't effect resources destination
  • 12393: Packaging should provide support for extensible categories
  • 14549: Recursive inclusion of packages