| 1 |
On 11/13/2014 05:30 AM, Michael Palimaka wrote: |
| 2 |
> |
| 3 |
> Suggested policy to get the ball rolling: |
| 4 |
> |
| 5 |
> In general, a package must explicitly depend upon what it directly uses. |
| 6 |
> However, to avoid ebuild complexity and developer burden there are some |
| 7 |
> exceptions. Packages that appear in the base system set may be omitted |
| 8 |
> from an ebuild's dependency list in the following circumstances: |
| 9 |
> |
| 10 |
> * C compiler and runtime |
| 11 |
|
| 12 |
Specifically sys-devel/gcc and sys-libs/glibc (i.e. what's in @system), |
| 13 |
or just anything? |
| 14 |
|
| 15 |
> * C++ compiler and runtime |
| 16 |
|
| 17 |
Isn't it possible to disable C++ in GCC with USE="-cxx"? |
Archives