| 1 |
On Wed, 29 May 2013 19:22:32 -0500 |
| 2 |
William Hubbs <williamh@g.o> wrote: |
| 3 |
|
| 4 |
> > For the same reason we have all the other eselect modules. |
| 5 |
> |
| 6 |
> We could probably also turn gcc-config into an eselect module if we |
| 7 |
> want to use that argument. |
| 8 |
|
| 9 |
Looking at Duncan's reply, that has already happened in the past. |
| 10 |
|
| 11 |
Really, think about it, why do we have all those eselect modules at all? |
| 12 |
Why be inconsistent and not introduce one here? Why keep them around? |
| 13 |
|
| 14 |
Well, the answer is simple: |
| 15 |
|
| 16 |
Remember that eselect init is optional and an opt-in by emerging it, |
| 17 |
this is in no way suggested anywhere to become a default on all systems. |
| 18 |
|
| 19 |
If you don't want it, fine, but that doesn't stop us from pursuing it... |
| 20 |
|
| 21 |
-- |
| 22 |
With kind regards, |
| 23 |
|
| 24 |
Tom Wijsman (TomWij) |
| 25 |
Gentoo Developer |
| 26 |
|
| 27 |
E-mail address : TomWij@g.o |
| 28 |
GPG Public Key : 6D34E57D |
| 29 |
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D |
Archives