On 11.07.2017 23:23, Adam Borowski wrote:

> Uhm, but what's the point in _this_? Samba does the right thing: builds
> systemdD support if and only if its configure script detected the headers
> (which can usually also be forced by --enable-foo or --disable-foo).

#1: just a little hack while waiting for the coffee compiler
#2: sends a clear message
#3: i'm too lazy to adapt configure calls in lots on lots of different
     buildsystems, so I patch it at one central point
#4: when upstream changes something here, I'll see it on next rebase
     (merge conflict)
#5: usually, when I come around bad code, i just kill it
#6: i dont trust upstreams, neither do i trust their configure scripts

Whether or not packagers follow this approach, or another one, is
entirely their decision. (not my business).

OTOH, it's just a trivial example. Other packages might actually need
patching. In that case I'd just rip off the lennartware, instead of
make it (build-time) optional.

My whole point wasn't about that particular case, but the idea of
collecting depotterized maintenance branches in one community, where
everybody can easily pick them.


--mtx