Just a note about include files in ports

[Michael Nottebrock]

On Tuesday, 29. November 2005 21:40, Kris Kennaway wrote:
> On Tue, Nov 29, 2005 at 02:25:09PM -0500, Diane Bruce wrote:
> > Hi,
> >
> > Be careful with includes in a port build. I have caught two ports using
> > the include files installed by a previous version of the port instead
> > of the local port copy of the same include file. (Yes, one was in one
> > of my own ports.) In particular, configure args that put the -I
> > to /usr/local/include or /usr/X11/include before the -I
> > ${WRKSRC}/..../include can break or at least compile incorrectly if the
> > port include files change between releases. If you are lucky, it will
> > fail.
>
> Parts of KDE and GNOME do this :-( It's one of the main reasons that
> 'portupgrade' doesn't just work for upgrading them.

No, at least as far as KDE is concerned, it's not. The KDE developers like to 
make their packagers' lifes harder in much more blunt ways (such as moving 
files around from one module into another in-between point releases). =/

-- 
   ,_,   | Michael Nottebrock               | lofi at freebsd.org
 (/^ ^\) | FreeBSD - The Power to Serve     | http://www.freebsd.org
   \u/   | K Desktop Environment on FreeBSD | http://freebsd.kde.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20051129/cd19d558/attachment.bin