| 1 |
2009/11/26 Brian Harring <ferringb@×××××.com>: |
| 2 |
> Why is this one special? Two out of three do this already, and it |
| 3 |
> works. |
| 4 |
|
| 5 |
You mean "two out of three blatently ignored long-standing behaviour |
| 6 |
and added a new feature without discussion or an EAPI bump". |
| 7 |
|
| 8 |
> Paludis doesn't preserve mtime |
| 9 |
|
| 10 |
You mean "Paludis carefully emulated Portage behaviour, and is now |
| 11 |
somehow being blamed for the whole matter, to the extent that people |
| 12 |
are trying to use threats (to the effect of 'I'm going to deliberately |
| 13 |
break packages for Paludis users") to try to get their way in the |
| 14 |
discussion". |
| 15 |
|
| 16 |
> and it's approach to randomly resetting mtimes |
| 17 |
|
| 18 |
There's nothing random about it. Files' mtimes are reset to the |
| 19 |
current time while being merged, just as Portage did for years. |
Archives