| 2014-05-02 09:51:51 |
Chris Coulson |
description |
1) Availability
It's available on all architectures.
2) Rationale
ninja-build is now a hard build requirement for Oxide which is in main. As Google are explicitly disabling support for building Chromium with GYP's makefile backend**, it will also be a requirement for Chromium too (although Chromium isn't in main, yet). Chromium from the dev channel is not buildable with GYP's makefile backend, and Google have no plans to resolve this.
** see https://chromium.googlesource.com/chromium/src/build/+/9bc1c207a18ffa8284095d9350e835a4518870f6
3) Security
- No open issues
- No executables with suid or sgid bit set
- No executables in /sbin or /usr/sbin
- No daemon
- Doesn't open any ports
- Doesn't add plugins to security sensitive software, although it does provide bash-completion, zsh completion, vim and emacs plugins
4) QA
- Works after installing with no additional effort.
- Package does not ask debconf questions.
- No outstanding bugs. As this is the primary build tool used by Chrome developers, it would be reasonable to assume that there are people who care a lot for this.
- There is 1 important bug in Debian's BTS, but this is sparc specific:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697268
- Upstream, there are 17 issues in the issue tracker that are marked as bugs. Out of these, 5 are Windows specific. None are particularly important, and don't affect its use for building Oxide or Chromium:
https://github.com/martine/ninja/issues?labels=bug&page=1&state=open
- The package is currently sync'd from Debian. It's at version 1.3.4, and could probably do with updating to the latest release (1.4.0) which is the version used to build Chromium. The current version does work fine though.
- It builds a test binary, but doesn't appear to run this at the moment. It does use a python script to create a bootstrapped ninja binary, which it then uses to build itself.
- Has a debian/watch file.
5) UI standards
- N/A
6) Dependencies
debhelper, gtest, python, asciidoc, hardening-wrapper, re2c, help2man, libxslt, docbook-xsl, docbook-xml, doc-main - all in main.
7) Standards compliance
- No issues
8) Maintenance
- Package will be low maintenace. The current release (1.4.0) is 8 months old. The previous release (1.3.4) was 3 months before that. |
1) Availability
It's available on all architectures.
2) Rationale
ninja-build is now a hard build requirement for Oxide which is in main. As Google are explicitly disabling support for building Chromium with GYP's makefile backend**, it will also be a requirement for Chromium too (although Chromium isn't in main, yet). Chromium from the dev channel is not buildable with GYP's makefile backend, and Google have no plans to resolve this.
** see https://chromium.googlesource.com/chromium/src/build/+/9bc1c207a18ffa8284095d9350e835a4518870f6
3) Security
- No open issues
- No executables with suid or sgid bit set
- No executables in /sbin or /usr/sbin
- No daemon
- Doesn't open any ports
- Doesn't add plugins to security sensitive software, although it does provide bash-completion, zsh completion, vim and emacs plugins
4) QA
- Works after installing with no additional effort.
- Package does not ask debconf questions.
- No major long-term outstanding bugs. As this is the primary build tool used by Chrome developers, it would be reasonable to assume that there are people who care a lot for this.
- There is 1 important bug in Debian's BTS, but this is sparc specific:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697268
- Upstream, there are 17 issues in the issue tracker that are marked as bugs. Out of these, 5 are Windows specific. None are particularly important, and don't affect its use for building Oxide or Chromium:
https://github.com/martine/ninja/issues?labels=bug&page=1&state=open
- The package is currently sync'd from Debian. It's at version 1.3.4, and could probably do with updating to the latest release (1.4.0) which is the version used to build Chromium. The current version does work fine though.
- It builds a test binary, but doesn't appear to run this at the moment. It does use a python script to create a bootstrapped ninja binary, which it then uses to build itself.
- Has a debian/watch file.
5) UI standards
- N/A
6) Dependencies
debhelper, gtest, python, asciidoc, hardening-wrapper, re2c, help2man, libxslt, docbook-xsl, docbook-xml, doc-main - all in main.
7) Standards compliance
- No issues
8) Maintenance
- Package will be low maintenace. The current release (1.4.0) is 8 months old. The previous release (1.3.4) was 3 months before that. |
|
