| 1 |
> Thoughts? |
| 2 |
|
| 3 |
One point in favor of the current practice (installing add-on files |
| 4 |
unconditionally) is the fact that you can basically do it for free - you |
| 5 |
neither have to depend on additional packages, nor is the presence of |
| 6 |
the add-on files a penalty in download time or storage. |
| 7 |
|
| 8 |
Further, a lot of packages install _small_ additional files |
| 9 |
unconditionally - let it be examples, minimal documentation, example |
| 10 |
configurations - unconditionally. And this is done with the very same |
| 11 |
reasoning as above; the penalty is small enough to not warrant the |
| 12 |
introduction of a use flag. |
| 13 |
|
| 14 |
Personally, I would not introduce yet another set of global use flags |
| 15 |
just for the sake of controlling everything with use flags. The |
| 16 |
complexity this introduces (naming choice - enforcing the rule - |
| 17 |
ensuring uniformity) is worse than the current behavior of just |
| 18 |
installing small add-on files. |
| 19 |
|
| 20 |
Best, |
| 21 |
Matthias |
Archives