| 1 |
Hi, Igor |
| 2 |
|
| 3 |
LTHR <lanthruster@×××××.com> writes: |
| 4 |
|
| 5 |
> Portage QOS |
| 6 |
> |
| 7 |
> Hi All, |
| 8 |
> |
| 9 |
> What do you think about implementing this: |
| 10 |
> |
| 11 |
> http://forums.gentoo.org/viewtopic.php?p=7477494 |
| 12 |
> |
| 13 |
> I've system design in my head and could write it down with the |
| 14 |
> implementation details. |
| 15 |
> Then may be we could all review it and get to something we all agree |
| 16 |
> upon then I could |
| 17 |
> try getting a team and implement it. |
| 18 |
> |
| 19 |
> Just a brief question - does anyone know how many ebuilds are |
| 20 |
> assembled world |
| 21 |
> wide each second? |
| 22 |
|
| 23 |
This is quite impressive for me. I'm one who have been thinking like |
| 24 |
this. For the purpose, I started a Web service named GenTwoo on May |
| 25 |
2011: http://gentwoo.elisp.net/?locale=en |
| 26 |
|
| 27 |
First a GenTwoo user login with Twitter account to the service and |
| 28 |
installs a tiny script [1] on their Gentoo box. Then each time they run |
| 29 |
emerge, the script collect what package is emerged, if the emerge is |
| 30 |
succeed or failed, its elog output, and its build.log (only if the |
| 31 |
emerge failed). These information is sent to my server and tweeted |
| 32 |
periodically with "#gentwoo" hash tag so that you can see your friends are |
| 33 |
heating their computer :-). [2] |
| 34 |
|
| 35 |
You can also browse: |
| 36 |
|
| 37 |
- What all GenTwoo users emerge recently |
| 38 |
http://gentwoo.elisp.net/emerges?locale=en |
| 39 |
- What one user emerge recently |
| 40 |
http://gentwoo.elisp.net/users/naota344?locale=en |
| 41 |
- How a emerge failed (click "error log" tab) |
| 42 |
http://gentwoo.elisp.net/emerges/644259?locale=en |
| 43 |
- Recent popular packages |
| 44 |
http://gentwoo.elisp.net/poppackage?locale=en |
| 45 |
- How long dose it take to emerge a package (and its average) |
| 46 |
http://gentwoo.elisp.net/packages/app-text/poppler/?locale=en#0.24.5 |
| 47 |
|
| 48 |
Since I'm not much advertising the project, there are not so many active |
| 49 |
users (and they are mostly Japanese): there are only 54 users who ever |
| 50 |
emerged since Dec 2013. I'm not sure my GenTwoo project completely suit |
| 51 |
your demand, but there are already many emerge record on my server |
| 52 |
(645112 emerge records since the service started, and 22129 emerges |
| 53 |
since Dec 2013). So if you are interested, you can start "PortStat" or |
| 54 |
"PortStatDEV" implementation immediately with the emerge data I have. Or |
| 55 |
you can also join GenTwoo if you feel it's better to start from |
| 56 |
scratch. I'd appreciate it if you would join GenTwoo project and improve |
| 57 |
it together ;-) There's also on going project to rewrite GenTwoo into a |
| 58 |
package stat [3] |
| 59 |
|
| 60 |
Anyway, feel free to ask me GenTwoo's implementation detail if you are |
| 61 |
interested in it. I think I can help you write your design idea if you |
| 62 |
start from scratch with your idea. |
| 63 |
|
| 64 |
[1] https://github.com/naota/gentwoo/blob/master/client/gentwoo.py |
| 65 |
[2] https://twitter.com/search?q=%23gentwoo&f=realtime |
| 66 |
[3] https://github.com/gentoo/GenTwoo-backend/ |
| 67 |
|
| 68 |
Regards, |
Archives