4 ms·
The basic problem there is the mixing of feature changes and security changes in a single stream. So you can't just say you want security fixes only, no new or
by digi_owl 10y ago
The basic problem there is the mixing of feature changes and security changes in a single stream.
So you can't just say you want security fixes only, no new or changed features.
- btilly 10y agoThe problem with trying to separate them is that often a security fix is put into code that had feature changes, and so you can't get the security fix without the feature changes. Going the other way requires developers to maintain a variety of old versions of their code so they can backport security changes. Which is a lot of work for them for very little extra value.
- digi_owl 10y agoIOW you can't get a developer to do straight maintenance work...
- dredmorbius 10y agoHence Debian's practice of back-porting security fixes on stable distros. Also applies to Ubuntu, probably Red Hat, though the latter's vastly smaller repos mean vastly greater reliance on third-party sources, and concommitant risks of introducing/changing features when security fixes are wanted, or riding bareback without security updates. There's also the inherent conflict between running current code and fixed code. Debian's legendary conservatism reflects a bias toward the latter, at least on its stable branches. Of course, you're welcome to lead and bleed on testing, unstable, or experimental, if you so choose.