From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in sys-cluster/openmpi: ChangeLog openmpi-1.1.1.ebuild openmpi-1.2.4.ebuild
Date: Sat, 15 Dec 2007 01:51:47 +0000 (UTC) [thread overview]
Message-ID: <pan.2007.12.15.01.51.47@cox.net> (raw)
In-Reply-To: 4762DEE3.6060604@gentoo.org
Sébastien Fabbro <bicatali@gentoo.org> posted 4762DEE3.6060604@gentoo.org,
excerpted below, on Fri, 14 Dec 2007 19:52:03 +0000:
>> Hmm, i know this isn't a support list, but as it fits quite well: can
>> you tell me what configuration files I have to look for?
>
> At some point, one possibility was to create a
> /etc/portage/env/<cat>/<package> file with your own set of environment
> variables in it. But I have not checked lately if we can still do this.
Should still work, AFAIK (has been here on ~portage), but is portage
(package manager) specific and then only works on the bash side, not the
python side, so it won't always work as intended for stuff like features.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-12-15 2:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1J2dWi-0006Ue-Fk@stork.gentoo.org>
2007-12-13 9:18 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in sys-cluster/openmpi: ChangeLog openmpi-1.1.1.ebuild openmpi-1.2.4.ebuild Donnie Berkholz
2007-12-14 10:24 ` Matthias Langer
2007-12-14 12:13 ` Sébastien Fabbro
2007-12-14 14:12 ` Matthias Langer
2007-12-14 16:16 ` Sébastien Fabbro
2007-12-14 17:12 ` Matthias Langer
2007-12-14 19:52 ` Sébastien Fabbro
2007-12-15 1:51 ` Duncan [this message]
2007-12-14 14:53 ` [gentoo-dev] " Justin Bronder
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=pan.2007.12.15.01.51.47@cox.net \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-dev@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