...every day a little pondering, backstage information, jokes, tips and tricks.
22
Backstage
Some OpenPKG Statistics
The number of UNIX installations has
grown to 10, with more expected.
— The UNIX Programmer's Manual,
2nd Edition, June, 1972
At the end of this year we provide you some backstage numbers
from OpenPKG's CVS repository, OpenPKG-CURRENT, Release Engineering, Downloads,
etc.
CVS Repository
The OpenPKG CVS repository "
openpkg-src" module contains the
complete history of OpenPKG. It currently consists of
2750 files which
sum up to a total size of
52 MB and
1.95 million lines of text. During
6 years it evolved through 91600 commit transactions.
OpenPKG-CURRENT
OpenPKG-CURRENT is the development branch of OpenPKG. As of today,
it consists of
1048 individual software packages consisting of
4770 individual files:
2327 OpenPKG original files plus
2443 downloaded third-party files.
The
2327 OpenPKG original files are
346000 lines of text (with
10%
documentational comments). From these the
1048 primary package
specification files (
*.spec) are already
145000 lines of text
(with
19% documentational comments).
Release Engineering & Downloads
Over the last
5 years the OpenPKG release engineering produced
13 major releases. Between 2001-12 and 2006-12 they resulted in
49
million package downloads:
32.5 million downloads via FTP and
16.5
million downloads via RSYNC.
Security Engineering
Over the last
5 years the OpenPKG security engineering produced
nearly
200 security advisories corresponding to major security
issues in the packaged third-party software. Each major security
issue which affects OpenPKG requires between
1 man-day and
4 man-days for reviewing, back-porting, fixing, testing and
documentation. In addition, every week about
10 potential
security issues are reviewed in detail, too.
Development
Ralf S. Engelschall (aka "rse") is one OpenPKG's main developers. To
get an impression how the "development pipeline" of such an OpenPKG
developer looks, here are some numbers as of today: he currently has
72 pending potentially new packages (still either incomplete or
not tested enough),
37 pending modified package files (still
not acceptable for public consumption) and is on average working for
about
20 man-hours per week on dedicated OpenPKG development tasks
(software evaluations, package updates/upgrades, package improvements,
new packages, etc).
