Re: [gentoo-dev] Re: Implicit system dependency

[Ian Stakenvicius]

-----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.

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

>> * C++ compiler and runtime
>
> Isn't it possible to disable C++ in GCC with USE="-cxx"?

It is..  but unfortunately there's no way in DEPEND to ensure it's
satisfied, as you can have a gcc installed with that flag enabled but
have a second one (that's actually selected in gcc-config) with it
disabled.  A pkg_pretend check or a pkg_setup check (if you don't want
it to just fail in src_configure) is probably the best way to enforce
that one at this time.  Unless there are other ways I'm not aware of??

There's also the whole c++98 vs c++11 issue that's sort-of part of
this -- minimum clang version, minimum gcc version might relate.
Again though, afaik there's no easy way to deal with this in DEPEND.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iF4EAREIAAYFAlRky4AACgkQ2ugaI38ACPD1twD/da6rptWk1/vl2iDPSBWLmox2
5rXr7aEci8yCBoyDsk8A/0ZAGBtxlBWqoTGKzkJdm32pow4cOtFBEBO+YoVJkEyx
=xXHM
-----END PGP SIGNATURE-----