| 1 |
Mike Frysinger schrieb: |
| 2 |
>> A moderately knowledgeable user would notice that something is wrong |
| 3 |
>> from watching the build output for a couple of seconds. Portage however |
| 4 |
>> proceeds happily because make returns exit status 0. |
| 5 |
> |
| 6 |
> portage would always proceed. the only thing that would stop it is the user |
| 7 |
> hitting CTRL+C. and that requires the user actually be watching the build |
| 8 |
> output. perhaps they would be for a single package, but for general upgrades, |
| 9 |
> i doubt you can rely on that. what would be more likely is they try to run |
| 10 |
> `cdrecord`, find it missing, find the build failed, and then file a bug. that |
| 11 |
> workflow really isn't affected by the defaults here. |
| 12 |
> -mike |
| 13 |
|
| 14 |
In versions prior to cdrecord-3.00 it was actually the case that nothing |
| 15 |
at all was installed. That would cause patrick to notice and scroll back |
| 16 |
up in his terminal buffer now to see wtf went wrong. |
| 17 |
|
| 18 |
Since 3.00 it installs a cdrecord binary that runs but doesn't actually |
| 19 |
talk to hardware. Fun. |
| 20 |
|
| 21 |
|
| 22 |
Best regards, |
| 23 |
Chí-Thanh Christopher Nguyen |
Archives