From: "\"Paweł Hajdan, Jr.\"" <phajdan.jr@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] include files question
Date: Fri, 20 Sep 2013 09:03:14 -0700 [thread overview]
Message-ID: <523C71C2.3040807@gentoo.org> (raw)
In-Reply-To: <20130915170119.GA27140@linux1>
[-- Attachment #1: Type: text/plain, Size: 836 bytes --]
On 9/15/13 10:01 AM, William Hubbs wrote:
> All,
>
> here is another question wrt OpenRC's api.
>
> Currently we store two header files (rc.h and einfo.h) in /usr/include.
> Since we have more than one include file, wouldn't it be standard
> practice to store them in a sub directory of /usr/include?
I'm leaning towards having a directory for them like
/usr/include/openrc, but I'm also fine with having them in /usr/include .
It's not so much about standard practice, but even say avoiding file
collisions and weird issues with wrong headers being included
(especially rc.h seems to be a fairly generic name).
Also, it may be easier to change now when we only have two headers, than
later. And you may even add compatibility symlinks or copies in
/usr/include to give people more time to update.
Paweł
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 203 bytes --]
next prev parent reply other threads:[~2013-09-20 16:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-15 17:01 [gentoo-dev] include files question William Hubbs
2013-09-15 23:35 ` Ian Stakenvicius
2013-09-20 16:03 ` "Paweł Hajdan, Jr." [this message]
2013-09-20 16:12 ` Peter Stuge
2013-09-20 16:27 ` Michał Górny
2013-09-20 16:39 ` "Paweł Hajdan, Jr."
2013-09-21 11:00 ` Peter Stuge
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=523C71C2.3040807@gentoo.org \
--to=phajdan.jr@gentoo.org \
--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