1 |
On the issue of QA, I think enabling FEATURES="collision-detect" by default |
2 |
would do a lot more good at this stage than "test". There are several |
3 |
packages I have come across where this has picked up files not being |
4 |
removed from earlier versions. It's a reasonable default to have and |
5 |
doesn't involve delaying users since it takes a fraction of a second to |
6 |
carry out. What I'd propose is that portage runs the collision-detect and |
7 |
reports it, but continues the installation in the same manner as now. |
8 |
|
9 |
This could tie into an automated report at a later stage. |
10 |
|
11 |
According to the portage team the majority of blockers in the tree are |
12 |
`soft' blocks which are file collisions. I understand that they'd like to |
13 |
separate those from hard blocks which are more fundamental |
14 |
incompatibilities than installing the same file, since that would make it |
15 |
easier for QA to track those. collision-detect isn't going to help with |
16 |
that, of course, but I wonder what the issues would be with such a change? |
17 |
|
18 |
|
19 |
-- |
20 |
gentoo-dev@g.o mailing list |