From: "Richard Fish" <bigfish@asmallpond.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerging IFC - Intel Fortran Compiler
Date: Sat, 29 Jul 2006 17:14:49 -0700 [thread overview]
Message-ID: <7573e9640607291714r44c5a47al87d618666b7c86dc@mail.gmail.com> (raw)
In-Reply-To: <20060730000303.73053.qmail@web31812.mail.mud.yahoo.com>
On 7/29/06, Richard Broersma Jr <rabroersma@yahoo.com> wrote:
> Hello all,
>
> I am trying to install Fortran for a school project
> my wife is working on.
>
> Are there any installation instructions better
> than the following ones?:
>
> 1) http://bugs.gentoo.org/show_bug.cgi?id=117452
> - my question with this link is, where is this overlay
> directory that is mentioned?
This is talking about creating a local portage overlay for your own
ebuilds. You can set PORTDIR_OVERLAY=/usr/local/portage in
/etc/make.conf, and then create your own portage tree under
/usr/local/portage [1].
You really should not mess with overlays unless you really know what
you are doing. However, you generally start by either:
1. Copying an existing category/package directory from the official
tree, and hacking on it your overlay. This is useful if you want to
do a version bump or apply a patch that is not in the offical tree.
2. Creating your own category/package directory, and adding your own
ebuilds and/or patches.
Once you have created your ebuild, "ebuild <path_to_ebuild> digest"
will generate the MANIFEST and other necessary files.
However, dev-lang/ifc already exists. If you want the latest 9.0.031
version, you'll have to accept the ~arch keyword, but this is
certainly a lot easier than trying to maintain your own overlay.
-Richard
[1] http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=5
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-07-30 0:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-30 0:03 [gentoo-user] emerging IFC - Intel Fortran Compiler Richard Broersma Jr
2006-07-30 0:14 ` Richard Fish [this message]
2006-07-30 1:12 ` Richard Broersma Jr
2006-07-30 0:28 ` Donnie Berkholz
2006-07-30 1:16 ` Richard Broersma Jr
2006-07-30 1:38 ` Donnie Berkholz
2006-07-30 1:46 ` Richard Broersma Jr
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=7573e9640607291714r44c5a47al87d618666b7c86dc@mail.gmail.com \
--to=bigfish@asmallpond.org \
--cc=gentoo-user@lists.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