| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 19/09/12 09:09 AM, Michael Orlitzky wrote: |
| 5 |
> On 09/19/2012 06:59 AM, Duncan wrote: |
| 6 |
>> Ben de Groot posted on Wed, 19 Sep 2012 12:22:06 +0800 as |
| 7 |
>> excerpted: |
| 8 |
>> |
| 9 |
>>> On 16 September 2012 21:15, Brian Harring <ferringb@×××××.com> |
| 10 |
>>> wrote: |
| 11 |
>> |
| 12 |
>>>> So... basically, people are already doing this manually with |
| 13 |
>>>> their own intermediate vars. |
| 14 |
>>> |
| 15 |
>>> And this works fine, so it doesn't warrant a cosmetic change. |
| 16 |
>> |
| 17 |
>> @ferringb: |
| 18 |
>> |
| 19 |
>> yngwin has a point that I've not seen addressed. |
| 20 |
>> |
| 21 |
>> What /is/ wrong with the whole CDEPEND intermediate var idea? It |
| 22 |
>> seems to work and /I/ don't know of any problems with it (and it |
| 23 |
>> would appear, neither does yngwin), yet you talk about it as if |
| 24 |
>> there's something wrong with it. |
| 25 |
>> |
| 26 |
>> And while we're at it, do DEPEND="$RDEPEND ..." style solutions |
| 27 |
>> have the same problems (or lack thereof)? |
| 28 |
> |
| 29 |
> The problem appears as we introduce more DEPEND variables (which is |
| 30 |
> what prompted the proposal, IIRC). If we have ADEPEND, BDEPEND, |
| 31 |
> CDEPEND, and DDEPEND, and there's only some (i.e. not total) |
| 32 |
> sharing going on then the COMMON_DEPEND pattern starts to fall |
| 33 |
> apart. You potentially need, |
| 34 |
> |
| 35 |
> AB_DEPEND AC_DEPEND AD_DEPEND BC_DEPEND BD_DEPEND CD_DEPEND |
| 36 |
> ABC_DEPEND ABD_DEPEND ACD_DEPEND BCD_DEPEND ABCD_DEPEND |
| 37 |
> (COMMON_DEPEND) |
| 38 |
> |
| 39 |
> This obviously gets worse as more DEPEND vars are introduced. |
| 40 |
> |
| 41 |
|
| 42 |
Well not really, no -- the additional *DEPENDs that are being proposed |
| 43 |
(or at least mentioned) for new EAPI will either remove atoms from |
| 44 |
COMMON_DEPEND/DEPEND/RDEPEND or will be used so tersely that a |
| 45 |
COMMON_DEPEND or other intermediate variable won't really be necessary |
| 46 |
for them. |
| 47 |
|
| 48 |
Besides, this isn't actually a -problem- as there's nothing which |
| 49 |
really requires one to use such helpers; ebuild writers just, well, |
| 50 |
can. :) |
| 51 |
|
| 52 |
-----BEGIN PGP SIGNATURE----- |
| 53 |
Version: GnuPG v2.0.19 (GNU/Linux) |
| 54 |
|
| 55 |
iF4EAREIAAYFAlBZxZIACgkQ2ugaI38ACPDp4wD/atjvaOsi/ntDMB1Dj7lSAVmW |
| 56 |
45qKz6+OO+H/+6eFeVIA/Rz0s7FiG6d2frboHXpYrDBzM1FZcU85AqZti34tR8+h |
| 57 |
=E78Z |
| 58 |
-----END PGP SIGNATURE----- |
Archives