| 1 |
On Sun, 15 May 2016 04:18:39 -0700 |
| 2 |
Daniel Campbell <zlg@g.o> wrote: |
| 3 |
|
| 4 |
> On 05/15/2016 02:15 AM, Brian Dolbec wrote: |
| 5 |
> > On Sun, 15 May 2016 11:05:21 +0200 |
| 6 |
> > Jeroen Roovers <jer@g.o> wrote: |
| 7 |
> > |
| 8 |
> >> On Sat, 7 May 2016 23:25:58 +0200 |
| 9 |
> >> Michał Górny <mgorny@g.o> wrote: |
| 10 |
> >> |
| 11 |
> >>> Do you seriously expect this code to work? How about testing? Or |
| 12 |
> >>> reading diffs before committing? |
| 13 |
> >> |
| 14 |
> >> |
| 15 |
> >> Somebody could have a go at implementing this: |
| 16 |
> >> |
| 17 |
> >> https://bugs.gentoo.org/show_bug.cgi?id=390651 |
| 18 |
> >> |
| 19 |
> >> It's been brewing for half a decade. Maybe it's time. :) |
| 20 |
> >> |
| 21 |
> >> |
| 22 |
> >> Regards, |
| 23 |
> >> jer |
| 24 |
> >> |
| 25 |
> > |
| 26 |
> > With the new repoman code structure, yes, it would be a lot easier |
| 27 |
> > to implement. |
| 28 |
> > |
| 29 |
> > Also with the gen-b0rk test repo, that will be a good testing ground |
| 30 |
> > for eclass changes too. It just needs more devs to make test |
| 31 |
> > ebuilds to get it fully populated ;) |
| 32 |
> > |
| 33 |
> What sort of test ebuilds are you looking for? There are a few |
| 34 |
> packages I'd like to see get into Gentoo but I don't want to break |
| 35 |
> anything. :P |
| 36 |
> |
| 37 |
|
| 38 |
Have a look at the gen-b0rk repo, See how the ebuilds are done, follow |
| 39 |
those examples. There are lots more errors that repoman looks for that |
| 40 |
are not yet covered by test ebuilds. |
| 41 |
|
| 42 |
There are a few more in other areas of code, but here is the biggest |
| 43 |
list of errors/warnings that repoman can test for. |
| 44 |
|
| 45 |
https://gitweb.gentoo.org/proj/portage.git/tree/repoman/pym/repoman/qa_data.py?h=repoman |
| 46 |
|
| 47 |
-- |
| 48 |
Brian Dolbec <dolsen> |
Archives