From: Zach Forrest <diatribe@shaw.ca>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] standards/conventions? (LDPATH, include files)
Date: Thu, 06 Dec 2001 10:51:04 -0800 [thread overview]
Message-ID: <3C0FBE18.9000903@shaw.ca> (raw)
Are there any conventions on where to store include files? Also, when
should one not store files in /usr/lib and instead put a file in
/etc/env.d that sets LDPATH? The current package I'm working on defaults
to /usr/lib and /usr/include. I've looked in both of these directories
and it seems like it should be fine. Is this correct?
Zach
next reply other threads:[~2001-12-06 18:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-06 18:51 Zach Forrest [this message]
-- strict thread matches above, loose matches on Subject: below --
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
2001-12-07 10:10 ` Juergen Ilse
2001-12-07 14:33 ` Tod M. Neidt
2001-12-07 21:33 ` Daniel Robbins
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=3C0FBE18.9000903@shaw.ca \
--to=diatribe@shaw.ca \
--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