Packaging

(draft)

Tools/Technologies and Standards which assist to package and distribute a Subsystem (library, application) or a Functional Unit (Plugin).

Goals

  • Enable simple packaging and distribution across different Target environments
  • Keep genericity of language (products should work after an repository checkout)
  • Enable developers to work on different versions in a simple manner

Directives

  • Protect creativity of developers by keeping

Requirements

  • Packaging functionality should work with source codes
    • Whenever possible, information should be obtained from the code itself
    • Annotations should be as close as possible to the annotated entitity
      • e.g. function-annotation
  • Redundancy should be avoided (even if autogenerated)
    • If needed, e.g. for speed-improvement: should be optionally
    • If necessary: should be limited to domain (not included in all packaging forms)
      • e.g. a target OS, which depends on special formatted information of packages.

Candidates

Setuptools

SETUPTOOLS - Loading Eggs which do not have an egg_info