| 1 |
On Wednesday 19 August 2009, Duncan wrote: |
| 2 |
> FWIW, It'd be useful to know about @system packages as well, |
| 3 |
> particularly portage, I'd guess, and there's likely others. AFAIK |
| 4 |
> smolt depends on portage ATM, but the particular versions installed |
| 5 |
> and percentage for each could be /very/ helpful as more people run |
| 6 |
> smolt. |
| 7 |
|
| 8 |
There's definately interesting numbers in the packages people have |
| 9 |
installed that are not in the world file. Judging from the page |
| 10 |
Sebastian prepared a table "Non-world-file packages", which can |
| 11 |
list "other" ebuilds. The table cannot list all packages anyone has |
| 12 |
installed, but maybe a selected number of ebuilds. Another interface |
| 13 |
(query form, sql export, or regular custom reports) could then allow |
| 14 |
maintainers to query for specific packages or combinations. |
| 15 |
|
| 16 |
|
| 17 |
> And is there an anonymous ID number or other means taken to ensure |
| 18 |
> that a user that reports daily is going to refresh his own stats, but |
| 19 |
> not crowd out the guy reporting monthly or quarterly? |
| 20 |
|
| 21 |
Yes, the client associates its submits with a uuid it stores locally, |
| 22 |
and the server will update the client's profile (deleting the old |
| 23 |
data). |
| 24 |
|
| 25 |
> How often /should/ we update? |
| 26 |
> Every time we sync and finish our routine updates? Only once a |
| 27 |
> quarter? |
| 28 |
|
| 29 |
Fedora (where Smolt originated) recommends people to submit once a month |
| 30 |
using a cron entry. But that was back when Smolt only supported |
| 31 |
Hardware and OS statistics (that change less often). Maybe a weekly |
| 32 |
schedule is more appropriate in Gentoo? I think the Fedora people will |
| 33 |
kill us though for the increased server load as they run the official |
| 34 |
receiving server (they currently have 100 000 people submitting each |
| 35 |
month). |
| 36 |
|
| 37 |
|
| 38 |
Robert |
Archives