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