Date: Fri, 25 Apr 2003 15:54:32 +1000 From: Darren Reed <darrenr@reed.wattle.id.au> To: Ruslan Ermilov <ru@freebsd.org> Cc: freebsd-bugs@freebsd.org Subject: Re: misc/44148: installworld in 4.7-STABLE does not installIPFilter related header files Message-ID: <200304250554.PAA03475@avalon.reed.wattle.id.au> In-Reply-To: <20030424192427.GA71112@sunbay.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In some email I received from Ruslan Ermilov, sie wrote: Checking application/pgp-signature: FAILURE -- Start of PGP signed section. > On Fri, Apr 25, 2003 at 04:18:45AM +1000, Darren Reed wrote: > > In some email I received from Ruslan Ermilov, sie wrote: > > > In the SHARED=symlinks case, /usr/include/netinet is > > > the symlink to /usr/src/sys/netinet. Hope this now > > > makes more sense. > > > > Is there any reason to not create a real /usr/include/netinet > > and then populate _that_ directory with symbolic links to each > > of the files, individually ? This should preserve the semantics > > of what "symlinks" is about. > > > The original purpose of "symlinks" was to provide symlinks > to /sys sources, it's the so-called "developer's mode", so > one doesn't need to worry about if he changes/adds/deletes > a header. > > We could create /usr/include/contrib/ipfilter/netinet, and > that will be consistent with kern.pre.mk. Those that need > it would just add -I/usr/include/contrib/ipfilter. How is > this? Well, at least it helps ports get things from <netinet/*> include lines. So this problem only appears to affect people using /usr/src more "heavily" than the standard user that will install FreeBSD and get a /usr/include/netinet populated with all the correct files ? I can see that moving IPFilter include files to /usr/include/ipfilter at some point in the future will be an even better solution - but not just yet. Darren
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200304250554.PAA03475>