| 1 |
On Tue, Nov 3, 2015 at 3:45 PM, Justin (jlec) <jlec@g.o> wrote: |
| 2 |
|
| 3 |
> On 02/11/15 23:38, William Hubbs wrote: |
| 4 |
> Hi William, |
| 5 |
> |
| 6 |
> but instead of adding |
| 7 |
> |
| 8 |
> DEPEND="||·( |
| 9 |
> >=dev-lang/go-1.4 |
| 10 |
> >=sys-devel/gcc-5.1.0:=[go] |
| 11 |
> |
| 12 |
> to ebuilds, you could create a virtual/go with that dependency and make all |
| 13 |
> packages depend on that instead of this || (). Maybe in future clang gets |
| 14 |
> also |
| 15 |
> support for go, then you would need to edit again all ebuilds. Having a |
| 16 |
> virtual |
| 17 |
> for that case is much simpler. This is how we are doing it for fortran. |
| 18 |
> |
| 19 |
> Another problem which you have with these split deps is the following. |
| 20 |
> Imagine |
| 21 |
> the user has gcc-5[go] installed, which fullfills the dependency |
| 22 |
> requirement. |
| 23 |
> But she selected gcc-4.9 as the active compiler, which doesn't have go |
| 24 |
> support. |
| 25 |
> |
| 26 |
The build will fail. For fortran we test in pkg_setup if we have a working |
| 27 |
> fortran compiler present. You would need to do the same for go compiler. |
| 28 |
> |
| 29 |
> Justin |
| 30 |
> |
| 31 |
> |
| 32 |
Pretty good ! I'll take it. thanks. |
| 33 |
|
| 34 |
-Leno Hou |
Archives