| 1 |
On Wed, 22 Jun 2011 09:15:35 +0200 |
| 2 |
justin <jlec@g.o> wrote: |
| 3 |
|
| 4 |
> On 21/06/11 16:18, Matt Turner wrote: |
| 5 |
> > On Tue, Jun 21, 2011 at 7:17 AM, justin <jlec@g.o> wrote: |
| 6 |
> >> HI, |
| 7 |
> >> |
| 8 |
> >> with the addition of the fortran-2.eclass, it is possible to |
| 9 |
> >> remove the USE=fortran from the default profiles. Any objections? |
| 10 |
> >> |
| 11 |
> >> justin |
| 12 |
> > |
| 13 |
> > Nope, I actually suggested this back in December, and no one |
| 14 |
> > bothered to respond. |
| 15 |
> > |
| 16 |
> > Sounds good to me, |
| 17 |
> > Matt |
| 18 |
> > |
| 19 |
> |
| 20 |
> Removing fortran and adding an dependency on virtual/fortran lets |
| 21 |
> portage select dev-lang/ifc as the fortran compiler of choice. |
| 22 |
|
| 23 |
That's because portage doesn't suggest USE changes for one-of deps, and |
| 24 |
just falls back to first USE-clean option. |
| 25 |
|
| 26 |
> I reverted it back temporarily, so everything should be fine now |
| 27 |
> again. |
| 28 |
|
| 29 |
As said on IRC, if you really intend to do a thing like that, you |
| 30 |
should re-enable fortfran on the gcc package by default. |
| 31 |
|
| 32 |
-- |
| 33 |
Best regards, |
| 34 |
Michał Górny |
Archives