From: Daniel Robbins <drobbins@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] standards/conventions? (LDPATH, include files)
Date: Fri, 7 Dec 2001 15:31:22 -0600 [thread overview]
Message-ID: <20011207153122.F9706@chiba.3jane.net> (raw)
In-Reply-To: <20011207115617.B23974@ilse.asys-h.de>
On Fri, Dec 07, 2001 at 11:56:17AM +0100, Juergen Ilse wrote:
> > However, it doesn't actually get exported to your shell. Instead, env-update
> > changes /etc/ld.so.conf to include those dirs.
>
> IMHO is that "the right thing" to do.
Agreed. :)
--
Daniel Robbins <drobbins@gentoo.org>
Chief Architect/President http://www.gentoo.org
Gentoo Technologies, Inc.
next prev parent reply other threads:[~2001-12-07 21:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-06 19:33 [gentoo-dev] standards/conventions? (LDPATH, include files) tneidt
2001-12-06 19:43 ` Dan Armak
2001-12-06 20:47 ` Zach Forrest
2001-12-06 20:53 ` Dan Armak
2001-12-06 22:05 ` Zach Forrest
2001-12-07 10:56 ` Juergen Ilse
2001-12-07 14:54 ` Tod M. Neidt
2001-12-07 21:31 ` Daniel Robbins [this message]
2001-12-07 10:10 ` Juergen Ilse
2001-12-07 14:33 ` Tod M. Neidt
2001-12-07 21:33 ` Daniel Robbins
-- strict thread matches above, loose matches on Subject: below --
2001-12-06 18:51 Zach Forrest
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=20011207153122.F9706@chiba.3jane.net \
--to=drobbins@gentoo.org \
--cc=gentoo-dev@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