Gecko [ oric.aiou.edu.pk ]

Name	Size	Permission
README.examples	1.36 KB	-rw-r--r--
gensections.pl	509 B	-rwxr-xr-x
popanal.py	8.23 KB	-rwxr-xr-x
popcon-process.sh	2.52 KB	-rwxr-xr-x
popcon-stat.pl	5.67 KB	-rwxr-xr-x
popcon.pl	19.84 KB	-rwxr-xr-x
prepop.pl	2.29 KB	-rwxr-xr-x

Code Editor : README.examples

This directory contains some scripts used to post-process popularity-contest
entries.  You should have a lot of submissions from different users (at
least 100 of them, if possible) for these results to be valid.

To collect results, use procmail or some other mail alias to e-mail
submissions to a file called, say, new-popcon-entries.

You should run popcon-process.sh once a day, or so.  It calls prepop.pl to
split the mailbox file into a directory (popcon-entries) with one file per
submission, and only one submission per participant.  (Since each
participant makes a submission once per week, it's very important to
remove duplicates.)

HINT: if you have an account on popcon.debian.org, you can find a pre-processed
popcon-entries directory in /srv/popcon.debian.org/popcon-mail.  Feel free to
use these files to generate your own statistics.

Now you can do, for example:

cat popcon-entries/*/* | popanal.py

which creates a file named results.  Output lines look like this:

<name> is the package name;
<vote> is the number of people who use this package regularly;
<old> is the number of people who installed, but don't use this package
	regularly;
<recent-ctime> is the number of people who upgraded this package recently;
<no-files> is the number of people whose entry didn't contain enough
	information (atime and ctime were 0).

${this.title}

Code Editor : README.examples