This is the mail archive of the
libc-ports@sources.redhat.com
mailing list for the libc-ports project.
Re: Question on "never use the ports/ name in code or in log entries"
- From: Daniel Jacobowitz <drow at false dot org>
- To: Lior Balkohen <balkohen at gmail dot com>
- Cc: libc-ports at sources dot redhat dot com
- Date: Thu, 23 Feb 2006 09:21:49 -0500
- Subject: Re: Question on "never use the ports/ name in code or in log entries"
- References: <196b7d310602230616l43d02662v@mail.gmail.com>
On Thu, Feb 23, 2006 at 03:16:26PM +0100, Lior Balkohen wrote:
> Mentioned from Roland, we may not use the ports/ name in code or in
> log entries. But a simple grep -R -e '<ports/' in ports results that
> people have already used ports/ name in code.
>
> Can someone tell me an elegant solution how to fix this issue without
> using ports/ or - more horribly - paths like <../../...> to the
> correct headers, since this is always a problem for machines they have
> been in the official glibc source tree before and moved to the ports
> now?
Take a look at some of the other ways it's been fixed. In most cases
a path starting from <sysdeps/...> is OK; that will only match the
top level of glibc, the top level of ports, and the thread libraries.
--
Daniel Jacobowitz
CodeSourcery