| 1 |
On 4/20/07, Rob C <hyakuhei@g.o> wrote: |
| 2 |
> On 19/04/07, Christian Faulhammer <opfer@g.o> wrote: |
| 3 |
> > Arch teams normally have collision-protect enabled when doing |
| 4 |
> > keywording/stabling....in my eyes this is sufficient. |
| 5 |
> Its obviously not, Many users are reporting file-collisions on a weekly |
| 6 |
> basis. So either this isn't sufficient or the arch teams are not acting as |
| 7 |
> you describe. |
| 8 |
|
| 9 |
This can't be done yet, there's a couple of minor issues to iron out |
| 10 |
(some python and gcc stuff collisions). After those few remaining |
| 11 |
issues get finished, yeah this would be a useful default FEATURE. |
| 12 |
There's quite a couple of bugs (usually pretty cryptic ones) caused by |
| 13 |
clobbering files that belong to other ebuilds. |
| 14 |
|
| 15 |
@Opfer: Users will usually notice many more of those collisions simply |
| 16 |
because they are testing on a system that they normally use, while |
| 17 |
developers are often testing in chroots or test boxes with just the |
| 18 |
bare-bones system installed. |
| 19 |
|
| 20 |
-- |
| 21 |
|
| 22 |
Jakub Moc |
| 23 |
Email: jakub.moc@×××××.com |
| 24 |
-- |
| 25 |
gentoo-dev@g.o mailing list |
Archives