lp:~knitzsche/+junk/lp-stats

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

29. By Kyle Nitzsche <knitzsche@chroma> on 2010-09-28

improve comments

28. By Kyle Nitzsche <knitzsche@chroma> on 2010-09-28

common/templates/custom_html_reports_template.py: this is used when the
-c option is invoked. Also use -n to set the project name.

27. By Kyle Nitzsche <knitzsche@chroma> on 2010-09-28

move custom cmd line arg definitions below standard args, and add comment
to separate them.

also, add -n (--custom-name) options. this sets the project name in the
custom html page

26. By Kyle Nitzsche <knitzsche@chroma> on 2010-09-28

add the html template for custom projects

25. By Kyle Nitzsche <knitzsche@chroma> on 2010-09-28

make html h3 orange

24. By Kyle Nitzsche <knitzsche@chroma> on 2010-09-28

when a manifest is used to generate src pkgs to consider, some src pkgs
it returns are not in Ubunu main and thus they are excldued from the
working set. Since the final stats don't include these, they need to be
logged, and now they are, in reports/<type>-src-pkgs-not-found file.

23. By Kyle Nitzsche <knitzsche@chroma> on 2010-09-28

several big changes:
* changed main() method. Now it reflects the central flow with appropriate
method calls. control returns to the main method after each. each method
returns all data needed, which is then passed to other methods. As part
of this, the terminology is modifed and this is reflected in new generated
files.
 - 'superset' templates are those that are in the lp template export file
for the target release and that are enabled and, in the case of ubuntu,
that not removed as out of scope due to being in the EXTRA_SRC_PKGs list
 - 'working' templates are the superset after all blacklisting is applied
* logging: files are written into reports to show superset, working,
blacklist-file, blacklist-priority, blacklist-all (file names start with
'ubuntu' or 'custom'). Two methods do this for the two types of data
being written.
* implemented a new/better way to get the src pkgs for which data is
compiled in custom executions: from a manifest file (format per line:
'binary_pkg version'). The -m <file> argument enables and uses specified
file. Two methods parse the file.
 - get_bin_pkgs_from_manifest returns a list of tuples, where each tuple
is the binary pkg and its version
 - get_src_pkgs_from_binary_pkgs takes that list and returns correlated
src pkgs
then the domains for the found src pkgs are (if in LP template export
file) added to the working set of domains, which then is used to to create
the 'working' set.

22. By Kyle Nitzsche <knitzsche@chroma> on 2010-09-28

working commit

21. By Kyle Nitzsche <knitzsche@chroma> on 2010-09-27

added support for deriving list of languages from file specified with
cmd line arg from main script (-l <file>) instead of using the complete
set of langs returned by LP.

20. By Kyle Nitzsche <knitzsche@chroma> on 2010-09-27

Added parser cli argument to enable reading languages from file.