| 1 |
On Tue, May 13, 2014 at 1:28 AM, Andrew Savchenko <bircoph@×××××.com> wrote: |
| 2 |
> |
| 3 |
> Please do not enable them prior rigorous testing. |
| 4 |
> |
| 5 |
> I tried network-sandbox — this is a disaster. It brokes distcc |
| 6 |
> completely since distcc client can't connect to remote servers (and |
| 7 |
> even to a local one if any). |
| 8 |
|
| 9 |
Certainly agree on the need for testing, but it sounds like several |
| 10 |
have been using it without issue. Lack of distcc compatibility could |
| 11 |
be addressed by either filtering the setting if it is enabled, |
| 12 |
actually bridging the distcc traffic only, or by just publishing news |
| 13 |
to warn distcc users to disable it. |
| 14 |
|
| 15 |
I don't think that distcc compatibility should drive the defaults - |
| 16 |
distcc is not enabled by default and anybody using it should be able |
| 17 |
to handle reading a news item and complying. |
| 18 |
|
| 19 |
Rich |
Archives