|
|
Пишет LWN.net (![[info]](http://lj.rossia.org/img/syndicated.gif){kind=small} syn_lwnheadline)@ 2016-04-07 12:30:00 |
 |
|
 |
|
|
|
|
|
|
 |
|
 |
Hutterer: Why libinput doesn't have a lot of config options
Peter Hutterer writes
about the cost of configuration options.
"You see, whenever you write 'it's just 5 lines of code to make this
an option', what I think is 'once the patch is reviewed and applied, I'll
spend two days to write test cases and documentation. I'll need to handle
any bug reports related to this, and I'm expected to make sure this option
works indefinitely. Any addition of another feature may conflict with this
option, so I need to make sure the right combination is possible and test
cases are written.' So your work ends after writing a 5 line patch, my work
as maintainer merely starts."
Peter Hutterer writes
about the cost of configuration options.
"You see, whenever you write 'it's just 5 lines of code to make this
an option', what I think is 'once the patch is reviewed and applied, I'll
spend two days to write test cases and documentation. I'll need to handle
any bug reports related to this, and I'm expected to make sure this option
works indefinitely. Any addition of another feature may conflict with this
option, so I need to make sure the right combination is possible and test
cases are written.' So your work ends after writing a 5 line patch, my work
as maintainer merely starts."
