1 |
On 08/20/2015 07:42 PM, Michał Górny wrote: |
2 |
> Hi, |
3 |
> |
4 |
> Right now, a number of game packages are using USE=dedicated to control |
5 |
> 'installing a dedicated game server only'. Aside to that, some game |
6 |
> packages also have USE=server that controls building the server itself. |
7 |
> Non-game package use USE=client and USE=server. |
8 |
> |
9 |
> In order to improve uniformity of USE flags across different packages, |
10 |
> the QA team would like to deprecate USE=dedicated and use USE=client |
11 |
> and USE=server as appropriate. |
12 |
> |
13 |
> The problems I see with USE=dedicated are: |
14 |
> |
15 |
> - it is game-specific. The term 'dedicated server' is not used amongst |
16 |
> other server/client model packages. |
17 |
> |
18 |
> - It uses negative logic. Instead of enabling something, it disables |
19 |
> client. Pretty much 'dedicated' == 'noclient'. Negative logic is |
20 |
> confusing. |
21 |
> |
22 |
> - In packages having USE=server as well, it can lead to really absurd |
23 |
> combinations, like what does 'USE=dedicated -server' mean? Will it |
24 |
> build no executables at all? If we add REQUIRED_USE='dedicated? |
25 |
> ( server )', this gets quite unfriendly. |
26 |
> |
27 |
> As an alternative, we would use USE=client and USE=server along with |
28 |
> proper IUSE defaults to control client & server builds appropriately. |
29 |
> Both flags use positive logic, and REQUIRED_USE='|| ( client server )' |
30 |
> is rather clear. |
31 |
> |
32 |
> Does anyone see any real problems with that? |
33 |
> |
34 |
|
35 |
That increases the burden of managing configuration and further abuses |
36 |
REQUIRED_USE where it wasn't meant to be used in the first place. |
37 |
|
38 |
USE="dedicated" has worked fine for games users and no one has ever |
39 |
complained. In fact, it is a _very_ convenient USE flag, which means "no |
40 |
manual fiddling, this will be dedicated for sure". |
41 |
|
42 |
-1 |