1 |
On 14/11/14 01:05, Michael Orlitzky wrote: |
2 |
> On 11/13/2014 05:30 AM, Michael Palimaka wrote: |
3 |
>> |
4 |
>> Suggested policy to get the ball rolling: |
5 |
>> |
6 |
>> In general, a package must explicitly depend upon what it directly uses. |
7 |
>> However, to avoid ebuild complexity and developer burden there are some |
8 |
>> exceptions. Packages that appear in the base system set may be omitted |
9 |
>> from an ebuild's dependency list in the following circumstances: |
10 |
>> |
11 |
>> * C compiler and runtime |
12 |
> |
13 |
> Specifically sys-devel/gcc and sys-libs/glibc (i.e. what's in @system), |
14 |
> or just anything? |
15 |
|
16 |
Since they can be (in theory) replaced with some other implementation, |
17 |
anything unless there's a reason (like a binary package explicitly |
18 |
linking to glib). |
19 |
|
20 |
> |
21 |
>> * C++ compiler and runtime |
22 |
> |
23 |
> Isn't it possible to disable C++ in GCC with USE="-cxx"? |
24 |
|
25 |
It is, but I think if that's disabled you're on your own. :-) |