This is the mail archive of the
libc-ports@sources.redhat.com
mailing list for the libc-ports project.
Question on "never use the ports/ name in code or in log entries"
- From: "Lior Balkohen" <balkohen at gmail dot com>
- To: libc-ports at sources dot redhat dot com
- Date: Thu, 23 Feb 2006 15:16:26 +0100
- Subject: Question on "never use the ports/ name in code or in log entries"
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=IXujKRIcjUCN4pJlJvGCEKnLcp0A1OX6rL2769Qglv9i+Mml0Sys7evTI3hKamPTGKf6SsCrwyYGSsDkkt6l9rYb49giZWxZR1CzZ7W5j5sXp6M6AjOadT2BWwSDqKfxhgSJAZzCW+vPeLtlr/wW5QCCuZNCAvcUn8iwzOf+NHU=
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?
TIA.