| 1 |
hasufell <hasufell@g.o> wrote: |
| 2 |
> |
| 3 |
> Many defaults gentoo sets do not have anything to do with default |
| 4 |
> codepaths upstream has tested. |
| 5 |
|
| 6 |
I disagree: The USE-enabling in ebuilds usually follows upstream. |
| 7 |
IIRC there was even a policy for gentoo developers which strongly |
| 8 |
suggested this. |
| 9 |
|
| 10 |
> As above, our defaults are not necessarily following upstream |
| 11 |
> recommendations/defaults. Apache alone should make you think about that |
| 12 |
> claim. |
| 13 |
|
| 14 |
I never installed apache. |
| 15 |
However, especially for packages for which the choice of algorithms |
| 16 |
has to be selected (USE-flags thread, jit) or of protocols/interfaces |
| 17 |
(openssl or gnutls, neon or other, sqlite or mysql, openvpn[lzo], |
| 18 |
qtgui[exceptions], mesa, freetype, wine), the installation of tools |
| 19 |
(utils, examples, tk, perl, python) or extensions (tls-heartbeat, |
| 20 |
introspection, X, readline) the defaults usually follow the |
| 21 |
upstream default or recommendation unless there is a severe reason |
| 22 |
not to. |
| 23 |
|
| 24 |
> If disabling one useflag breaks the whole package, then it's a bug. |
| 25 |
|
| 26 |
Whether it breaks your machine/setup or not is independent of |
| 27 |
whether it breaks a package. |
| 28 |
|
| 29 |
> care about and arch testers usually run all(or most?) useflag |
| 30 |
> permutations before stabilizing. |
| 31 |
|
| 32 |
Simple mathematics shows that this cannot be even closely true. |
| 33 |
Anyway, this has nothing to do with our discussion. |
Archives