*** xref:Golang_templates.adoc[Additional annotated templates]

  ** xref:Haskell.adoc[Haskell]

  ** xref:Java.adoc[Java]

  ** xref:JavaScript.adoc[JavaScript]

  ** xref:Lisp.adoc[Lisp]

  ** xref:Mono.adoc[Mono]

  == Using Cython[[_packages_using_cython]]

  Tightening the

  packages *MUST NOT* use files pre-generated by Cython.

  These *MUST* be deleted in `+%prep+` and regenerated during the build.

  == Python 2 packages

  If your package needs to build for Python 2 only,

  except substitute 3 for 2.

  For example instead of `+%{python3_sitearch}+`,

  use `+%{python2_sitearch}+`.

  * An exception is made for binary firmware, as long as it meets the requirements documented https://fedoraproject.org/wiki/Licensing:Main#Binary_Firmware[here].

  * Some pre-packaged program binaries or program libraries may be under terms which do not permit redistribution, or be affected by legal scenarios such as patents. In such situations, simply deleting these files in %prep is not sufficient, the maintainer will need to make a modified source that does not contain these files. See: xref:SourceURL.adoc#when-upstream-uses-prohibited-code[When Upstream uses Prohibited Code].

  == Pregenerated code

  Often a package will contain code which was itself generated by other code. This often takes the form of configure files or parsing code generated by bison/yacc or lex/flex.