-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 07/09/12 02:46 PM, Michał Górny wrote: > On Fri, 7 Sep 2012 19:31:16 +0100 Ciaran McCreesh > <ciaran.mccre...@googlemail.com> wrote: > >> On Fri, 7 Sep 2012 20:23:23 +0200 Michał Górny >> <mgo...@gentoo.org> wrote: >>> I can't agree unless I am missing something. Doesn't the >>> majority of ebuilds actually require most of DEPEND (well, the >>> part common with RDEPEND) to be installed on the target? I'm >>> thinking of the shared libraries mostly. >> >> "The part common with RDEPEND" is a different issue. We're >> talking about what the usual thing to do is for dependencies that >> are in DEPEND but not RDEPEND. A typical example here is a binary >> that is executed as part of the build process. > > Thanks for keeping me on the topic. > > Now, let me remind you because you probably fail to know the world > outside your dreamworld: > > (with HDEPEND/DEPEND) generally mean that we would need to > s/DEPEND/HDEPEND/ for the vast majority of ebuilds (ie all the > trivial ones)? > > That does effectively refer to the common depends as well. You > know, in the real world where there is no magical variables which > do miracles behind your back. >
RDEPEND is defined in an earlier post (by Zac i think?) as target build+run dependencies; there are very few actual target build-only dependencies (ie, deps that need to be installed on the target and don't need to be installed on the host, and don't need to be on the target after build time). As such, HDEPEND since it means build-host build-time deps will still need to have these common dependencies specified but that doesn't have anything to do with the target's requirements, which right now are already entirely covered by RDEPEND (and not DEPEND) at all. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iF4EAREIAAYFAlBKTg0ACgkQ2ugaI38ACPBZJwD9E9MT2ZVsKtY+VujuMYjhi5EC B0RfyRnpXHu4JraBh+0A/014AWaOO3x70axEfdzTFbygRepDe6LWPqFy71nxBC3v =7hsL -----END PGP SIGNATURE-----
