
Code: Select all
We now have 1834 entries.Code: Select all
curl -d "arch=$(uname -m)&packages=$(qlist -CI)" http://stats.larrythecow.org/
Thanks :) We now have 1834 entries.Code: Select all
We now have 1835 entries.

Code: Select all
r2d2 / # curl -d "arch=$(uname -m)&packages=$(eix -I --only-names)" http://stats.larrythecow.org/
Thanks :) We now have 1872 entries.

Created "bugs" for these four:AllenJB wrote:
- Top 10 packages in each category.
- Specific package versions that are not used by anybody (or by only a handful - less than 20 for example)
- Popularity over time graphs for each package
- Perhaps for each category too - identify which appears to be the most popular desktop environment for example
Does the report table on repositories answer that to your contentment?nightmorph wrote:Also, I'd like to see the number of users who have packages installed that are not from the Portage tree. Furthermore, of that group, what percentage of those packages are not available in the tree? It'd be interesting to see how many 3rd party resources, such as overlays, upstream ebuilds, or homebrewed standalone ebuilds, are in use.
With about 13,000 packages and a growing number of submissions that would strongly increase report generation time. I wonder if the resulting data would be any helpful as there will be high correlations to all sorts of unrelated packages, e.g. Amarok will have high correlations with Vim.ArneBab wrote:Relations between packages: Which packages are installed together with which other packages most of the time?
What dio you mean by "outstanding" GLSA? If there was something like repeatedly-updated XML file with all package names and versions that are affected by some sort of vulnerability integration into the report (e.g. marking packages red or linking to GLSAs) would be possible. Is there such thing?alistair wrote:2) If you have package version, which ones have outstanding GLSA's ( Tho it would be very inaccurate so maybe we should leave this one alone).
A table dedicated to text editors would be no problem. I wonder if the correlation would be worth the effort. Convince mealistair wrote:3) Maybe find all text editors and then have stats based on them, ie count, whether there are relationship between text editors. eg. if there a relatonship betwwen system with emacs also having kwrite ( or kate and vim ), etc ,etc
Please elaborate on that.node_one wrote:Bug statistics for the popular packages, maybe?

I wouldn't make that the default part, but rather something people can generate _by hand_, if they want to create a news article or similar.sping wrote:With about 13,000 packages and a growing number of submissions that would strongly increase report generation time. I wonder if the resulting data would be any helpful as there will be high correlations to all sorts of unrelated packages, e.g. Amarok will have high correlations with Vim.ArneBab wrote:Relations between packages: Which packages are installed together with which other packages most of the time?
Code: Select all
smolt processData --server=... --correllation="items:installed_packages,subjects=users"