1 |
On Mon, 13 Jan 2014 23:59:11 -0500 |
2 |
Mike Frysinger <vapier@g.o> wrote: |
3 |
|
4 |
> we have a bugzilla workflow doc posted which we'll merge once git is |
5 |
> back up. please do not reassign portage bugs to yourself. instead, |
6 |
> set the status to INPROGRESS. |
7 |
|
8 |
Okay, I will comment there later; since I now have a whole other vision |
9 |
of the bug workflow in my head due being asked to do this, I rather see |
10 |
the resulting workflow as more handy than the posted workflow doc. |
11 |
|
12 |
As a side note, those changes were with permission suggested by dol-sen. |
13 |
|
14 |
> > While vapier's case could be considered as valid; I think we should |
15 |
> > consider that as a bad practice, as one could just as well put the |
16 |
> > if inside a phase which is the much more common practice. |
17 |
> |
18 |
> certainly, but we need to notify the dev community first |
19 |
|
20 |
+1 |
21 |
|
22 |
> we probably should just use dev branches in the main repo, at least |
23 |
> for people who have write access to the repo |
24 |
> dev/$USERNAME/<whatever you want> |
25 |
|
26 |
To be more clear, which one? g.o.g.o, GitHub or is one of both fine? |
27 |
|
28 |
The suggested naming sounds good to me, I suggest we document that. |
29 |
|
30 |
> > r'\s*src_(configure|prepare)\s*\(\)' |
31 |
> > |
32 |
> > You can then proceed further and move the re outside: |
33 |
> |
34 |
> the idea was to walk a balance between simplicity and |
35 |
> maintainability. imo, the fixed version above is the best. |
36 |
|
37 |
What about the latter improvements about the parentheses? |
38 |
|
39 |
Yes, I agree that de-duplicating 're' is an overkill change with no |
40 |
benefit other than some non-measured performance; but, the latter |
41 |
changes contain a benefit in more correct matching of the parentheses. |
42 |
|
43 |
> > > the regex is naive and can match valid ebuilds. consider ones |
44 |
> > > that handle $EAPI itself and will call the right funcs as |
45 |
> > > necessary. |
46 |
> > |
47 |
> > From a QA point of view it seems more preferable to move away from |
48 |
> > old EAPIs, than to conditionally support them. The common case is |
49 |
> > that ebuilds move from older to newer EAPI and thus would get these |
50 |
> > functions as they get to a newer EAPI. |
51 |
> > |
52 |
> > Is there an actual case for downgrading back to an older EAPI? |
53 |
> > |
54 |
> > If not, conditional code that checks $EAPI has no purpose. |
55 |
> |
56 |
> and yet it exists today. |
57 |
|
58 |
Does that existence mean it has an actual purpose? Or is it just there? |
59 |
|
60 |
> as long as portage supports an EAPI, i see no reason to omit useful |
61 |
> checks like this. -mike |
62 |
|
63 |
Repeating my original question in different words: Why is it useful? |
64 |
|
65 |
-- |
66 |
With kind regards, |
67 |
|
68 |
Tom Wijsman (TomWij) |
69 |
Gentoo Developer |
70 |
|
71 |
E-mail address : TomWij@g.o |
72 |
GPG Public Key : 6D34E57D |
73 |
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D |