From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: jlec@gentoo.org
Subject: Re: [gentoo-dev] RFC Remove USE=fortran in default profile
Date: Wed, 22 Jun 2011 09:55:27 +0200 [thread overview]
Message-ID: <20110622095527.0a401392@pomiocik.lan> (raw)
In-Reply-To: <4E019697.8060905@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1003 bytes --]
On Wed, 22 Jun 2011 09:15:35 +0200
justin <jlec@gentoo.org> wrote:
> On 21/06/11 16:18, Matt Turner wrote:
> > On Tue, Jun 21, 2011 at 7:17 AM, justin <jlec@gentoo.org> wrote:
> >> HI,
> >>
> >> with the addition of the fortran-2.eclass, it is possible to
> >> remove the USE=fortran from the default profiles. Any objections?
> >>
> >> justin
> >
> > Nope, I actually suggested this back in December, and no one
> > bothered to respond.
> >
> > Sounds good to me,
> > Matt
> >
>
> Removing fortran and adding an dependency on virtual/fortran lets
> portage select dev-lang/ifc as the fortran compiler of choice.
That's because portage doesn't suggest USE changes for one-of deps, and
just falls back to first USE-clean option.
> I reverted it back temporarily, so everything should be fine now
> again.
As said on IRC, if you really intend to do a thing like that, you
should re-enable fortfran on the gcc package by default.
--
Best regards,
Michał Górny
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 316 bytes --]
next prev parent reply other threads:[~2011-06-22 7:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 7:17 [gentoo-dev] RFC Remove USE=fortran in default profile justin
2011-06-21 14:18 ` Matt Turner
2011-06-22 7:15 ` justin
2011-06-22 7:55 ` Michał Górny [this message]
2011-06-22 8:01 ` justin
2011-06-22 14:35 ` Matthew Summers
2011-06-22 14:47 ` Andreas K. Huettel
2011-06-22 15:16 ` justin
2011-06-22 19:17 ` James Cloos
2011-06-22 20:18 ` Mike Frysinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110622095527.0a401392@pomiocik.lan \
--to=mgorny@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=jlec@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox