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: Roland McGrath <roland at redhat dot com>
- To: "Lior Balkohen" <balkohen at gmail dot com>
- Cc: libc-ports at sources dot redhat dot com
- Date: Thu, 23 Feb 2006 13:58:47 -0800 (PST)
- Subject: Re: Question on "never use the ports/ name in code or in log entries"
> 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.
This should be fixed. The add-on may not be called that at all. There
should be adequate -Is to find everything. I am about to change around how
add-ons work, so I'll be sure to fix this so it works.
You don't use ports/ in ChangeLog entries because file names in log entries
are relative to the directory containing the ChangeLog file. For add-on
ports, each one has its own top-level ChangeLog.<cpu> file.
Thanks,
Roland