1 |
On Wed, 2013-01-23 at 01:15 -0200, Rafael Goncalves Martins wrote: |
2 |
> On Tue, Jan 22, 2013 at 10:57 PM, Brian Dolbec <dolsen@g.o> wrote: |
3 |
> > On Tue, 2013-01-22 at 14:44 +0100, Theo Chatzimichos wrote: |
4 |
> >> On Tue, Jan 22, 2013 at 2:25 PM, Petteri Räty <betelgeuse@g.o> wrote: |
5 |
> >> > On 13.1.2013 0.49, "Paweł Hajdan, Jr." wrote: |
6 |
> >> >> Please review attached automatically generated stabilization candidates |
7 |
> >> >> for January. |
8 |
> >> >> |
9 |
> >> >> I don't want to annoy people with automatically filed bugs, and at the |
10 |
> >> >> same time I also received lots of positive feedback about the effort to |
11 |
> >> >> keep the stable tree more up-to-date. |
12 |
> >> >> |
13 |
> >> >> I think the best way to proceed is to listen to that feedback and |
14 |
> >> >> continue the effort, while also keeping an updated list of exclusions |
15 |
> >> >> for packagers/herds that are actively stabilized by maintainers. |
16 |
> >> >> |
17 |
> >> > |
18 |
> >> > I have an RSS feed for this purpose at: |
19 |
> >> > |
20 |
> >> > http://gentoo.petteriraty.eu/stable.rss |
21 |
> >> > |
22 |
> >> > Sources are available here: |
23 |
> >> > |
24 |
> >> > https://github.com/betelgeuse/scripts/blob/master/rss-changelog |
25 |
> >> > |
26 |
> >> > Maybe this is something that should be pushed to official Gentoo |
27 |
> >> > infrastructure so more people know about it and use it? |
28 |
> >> |
29 |
> >> File a bug against us then, with all the information needed for the deployment |
30 |
> >> |
31 |
> >> Theo |
32 |
> >> |
33 |
> > I had a look at the script, unfortunately (for me), it's both a ruby |
34 |
> > script and deps on paludis to get the information. |
35 |
> > |
36 |
> > Personally I think this would work well, but re-written in python and |
37 |
> > use portage for info. As euscan is all about scanning for upgradeable |
38 |
> > pkgs, it is already getting updated pkg info, scanning metadata.xml, |
39 |
> > etc. using portage, gentoolkit, and custom code. So this would fit well |
40 |
> > with it. It is python, django based. It could also offer the rss feed |
41 |
> > in a web page with a search box, and/or integrate the candidates into |
42 |
> > the pkgs status reports it does. |
43 |
> > |
44 |
> > Second reason, I believe it is getting or already has deployment on |
45 |
> > gentoo infra servers. |
46 |
> > |
47 |
> > I pinged `fox` in #-www about it, Corentin <iksaif> wasn't online there |
48 |
> > at the time. cc'ing them here. |
49 |
> |
50 |
> I think that euscan would benefit of this feature, but the your |
51 |
> arguments against ruby/paludis aren't valid IMO. |
52 |
|
53 |
That's exactly why I put in the "(for me)" in that statement. |
54 |
|
55 |
> If the euscan guys |
56 |
> want to integrate the feature, nice. |
57 |
|
58 |
Since Euscan is python, django based and already using python interfaces |
59 |
to portage, gentoolkit. It would be logical to redo it in python. But |
60 |
I believe it is set up to be able to run pretty much any script/binary |
61 |
as well. |
62 |
|
63 |
If this script gets run on gentoo infra, then euscan can just use that |
64 |
feed for display and add code to parse it for it's other reports. |
65 |
|
66 |
It is likely simpler for euscan to add picking up the additional data to |
67 |
produce the stabilization reports/feeds while it is scanning the newly |
68 |
sync'd tree and updating it's db. Producing the rss feed is simple at |
69 |
that point. Plus the data for other report formats would already be in |
70 |
it's db, making the rest of the displays simpler. |
71 |
|
72 |
|
73 |
> If not, lets just stick with this |
74 |
> script. |
75 |
|
76 |
Let's wait to hear from Corentin and Federico on it... |
77 |
|
78 |
> It is simple enough that even ruby n00bs like me can |
79 |
> understand what it does :P |
80 |
> |
81 |
> BR. |
82 |
> |
83 |
> |
84 |
|
85 |
It is for me too. |
86 |
|
87 |
> -- |
88 |
> Rafael Goncalves Martins |
89 |
> Gentoo Linux developer |
90 |
> http://rafaelmartins.eng.br/ |
91 |
> |
92 |
|
93 |
-- |
94 |
Brian Dolbec <dolsen@g.o> |