1 |
Am 27.05.2013 22:38, schrieb Anthony G. Basile: |
2 |
> Hi everyone, |
3 |
> |
4 |
> I was about to add a use expand flag for monkeyd (a tiny web server) and |
5 |
> there is a notice in base/make.default to discuss use expand flags on |
6 |
> the list first. There are about 9 plugins for monkeyd similar to apache |
7 |
> which can be turned on/off by a configure switch. It makes sense to |
8 |
> follow the same logic as apache here. There are no dependencies on |
9 |
> monkeyd and so no use-deps. Seems very safe. Any objections? |
10 |
> |
11 |
> --Tony |
12 |
> |
13 |
|
14 |
Some time ago, Zac proposed a general PLUGIN (or PLUGINS) use-expand, |
15 |
which could be used for packages with a small amount of plugins to avoid |
16 |
having a new USE_EXPAND for each and every package. It also has the |
17 |
advantage, that the resulting useflag 'plugins_foobar' is sane enough |
18 |
(opposed to 'monkeyd_plugins_foobar'). With this, it serves as a quite |
19 |
nice compromise for the fraction of USE_EXPAND-dislikers (like me). |
20 |
|
21 |
Unfortunately this did not get any real discussion. So could this |
22 |
package be an option to start this? Or do you insist on |
23 |
monkeyd_{plugins,modules,...}_ ? |
24 |
|
25 |
Thanks, |
26 |
René |