| 1 |
On Mittwoch, 4. August 2021 12:29:40 CEST Ulrich Mueller wrote: |
| 2 |
> >>>>> On Wed, 04 Aug 2021, Andreas Sturmlechner wrote: |
| 3 |
> > +# Standard dependencies string that is automatically added to BDEPEND |
| 4 |
> > +# (in EAPI-6: DEPEND) unless VIRTUALX_REQUIRED is set to "manual". |
| 5 |
> > +# DEPRECATED: Pre-EAPI-8 you can specify the variable BEFORE inherit |
| 6 |
> > +# to add more dependencies. |
| 7 |
> > +[[ ${EAPI} == [67] ]] || VIRTUALX_DEPEND="" |
| 8 |
> > +VIRTUALX_DEPEND+=" |
| 9 |
> > |
| 10 |
> > x11-base/xorg-server[xvfb] |
| 11 |
> > x11-apps/xhost |
| 12 |
> > |
| 13 |
> > " |
| 14 |
> > |
| 15 |
> > +[[ ${EAPI} == [67] ]] || readonly VIRTUALX_DEPEND |
| 16 |
> |
| 17 |
> I wonder about this one, because the *DEPEND variables are automatically |
| 18 |
> accumulated across eclasses and ebuild. What is the advantage of the |
| 19 |
> ebuild specifying VIRTUALX_DEPEND, instead of specifying BDEPEND |
| 20 |
> directly? |
| 21 |
> |
| 22 |
|
| 23 |
The answer is in the updated description in this patch: ebuilds/eclasses |
| 24 |
specifying VIRTUALX_REQUIRED=manual have (so far) been relying on the content |
| 25 |
of VIRTUALX_DEPEND to add the standard dependencies from within the ebuild |
| 26 |
instead of having virtualx.eclass do it for them, for whatever complex |
| 27 |
dependency situation they might have. |
Archives