1 |
On Wed, Jan 10, 2018 at 11:10 PM, Michał Górny <mgorny@g.o> wrote: |
2 |
> W dniu śro, 10.01.2018 o godzinie 21∶45 -0500, użytkownik Mike Gilbert |
3 |
> napisał: |
4 |
>> On Wed, Jan 10, 2018 at 5:56 PM, Zac Medico <zmedico@g.o> wrote: |
5 |
>> > On 01/10/2018 02:24 PM, Michał Górny wrote: |
6 |
>> > > Enable repoman checks on exp profiles by default to improve |
7 |
>> > > the dependency graph integrity on those profiles and help them on their |
8 |
>> > > way towards stable status. This is possible now that the dependency |
9 |
>> > > graph problems are warnings rather than errors. |
10 |
>> > > --- |
11 |
>> > > repoman/pym/repoman/argparser.py | 2 +- |
12 |
>> > > 1 file changed, 1 insertion(+), 1 deletion(-) |
13 |
>> > > |
14 |
>> > > diff --git a/repoman/pym/repoman/argparser.py b/repoman/pym/repoman/argparser.py |
15 |
>> > > index f32972288..d49147366 100644 |
16 |
>> > > --- a/repoman/pym/repoman/argparser.py |
17 |
>> > > +++ b/repoman/pym/repoman/argparser.py |
18 |
>> > > @@ -167,7 +167,7 @@ def parse_args(argv, qahelp, repoman_default_opts): |
19 |
>> > > |
20 |
>> > > parser.add_argument( |
21 |
>> > > '-e', '--include-exp-profiles', choices=('y', 'n'), metavar='<y|n>', |
22 |
>> > > - default=False, |
23 |
>> > > + default='y', |
24 |
>> > > help='include exp profiles in dependency checks') |
25 |
>> > > |
26 |
>> > > parser.add_argument( |
27 |
>> > > |
28 |
>> > |
29 |
>> > We have dev and exp profiles disabled by default because the time |
30 |
>> > consumed by repoman is proportional to the number of profiles. |
31 |
>> > |
32 |
>> > The current counts are as follows: |
33 |
>> > |
34 |
>> > stable 87 |
35 |
>> > dev 88 |
36 |
>> > exp 149 |
37 |
>> |
38 |
>> Yeah, I really don't like the idea of making repoman even slower by default. |
39 |
> |
40 |
> The alternative is to go for all profiles being stable. Because |
41 |
> accepting developers randomly breaking profiles 'because repoman speed' |
42 |
> is not acceptable. |
43 |
|
44 |
I disagree. Many of these are profiles that are seldom used and very |
45 |
few users are affected by any breakage. |
46 |
|
47 |
There's a balance to be struck here, and I think it's pretty good |
48 |
right where it is. |