El dom, 26-04-2015 a las 08:04 -0400, Rich Freeman escribió: > On Sun, Apr 26, 2015 at 5:59 AM, Pacho Ramos <pa...@gentoo.org> wrote: > > > > Currently, a problem is that everybody uses different formatting > > for stabilization bug reports making them more difficult to be parsed. > > > > For clarity, are we talking about parsing by a human brain, or parsing > by a computer program? > > If the latter, would it make more sense to just break things out into > fields, instead of carefully building a structured text field which we > then have to carefully break back down? We might as well start > sticking xml in the summary. > > If we're talking about human parsing, can you give an example of how > variation makes your life more difficult today? I'm just trying to > understand what we're trying to fix... >
About parsing it with scripts. For example, a script that could run periodically to fetch that lists, try to keyword them and see if repoman is ok with them or, otherwise, more deps need to be stabilized together. That would also allow us to easily fetch the list of packages + bugs we need to work on to, for example, emerge them (without needing to go to the list, copy the needed package atoms, paste them on a local file, go to the next bug...)
