> On Nov 15, 2014, at 3:57 PM, Matt Turner <matts...@gentoo.org> wrote: > >> On Thu, Nov 13, 2014 at 7:17 AM, Ian Stakenvicius <a...@gentoo.org> wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA256 >> >>> On 13/11/14 09:05 AM, 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? >> >> I would sincerely hope that nothing in the tree explicitly requires >> gcc as a C compiler. > > You say this, and then mention glibc in the next sentence. Glibc can > only be built with gcc. :) >
Sorry, I meant to say nothing other than toolchain-related packages :). Thanks for clarifying for me >> Glibc is a bit different, it may be necessary to explicitly depend on >> it (or use the elibc_glibc flag) if the package can't work with the >> libc alternatives, but ideally >
