Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 25 Apr 2003 09:22:47 +0300
From:      Ruslan Ermilov <ru@freebsd.org>
To:        Darren Reed <darrenr@reed.wattle.id.au>
Cc:        freebsd-bugs@freebsd.org
Subject:   Re: misc/44148: installworld in 4.7-STABLE does not install IPFilter related header files
Message-ID:  <20030425062247.GE32731@sunbay.com>
In-Reply-To: <200304250554.PAA03475@avalon.reed.wattle.id.au>
References:  <20030424192427.GA71112@sunbay.com> <200304250554.PAA03475@avalon.reed.wattle.id.au>

next in thread | previous in thread | raw e-mail | index | archive | help

--EXKGNeO8l0xGFBjy
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Apr 25, 2003 at 03:54:32PM +1000, Darren Reed wrote:
> In some email I received from Ruslan Ermilov, sie wrote:
>=20
> 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=3Dsymlinks case, /usr/include/netinet is
> > > > the symlink to /usr/src/sys/netinet.  Hope this now
> > > > makes more sense.
> > >=20
> > > 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.
> > >=20
> > 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.
> >=20
> > 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?
>=20
> 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 ?
>=20
I know many developers (not necessarily committers) still use
SHARED=3Dsymlinks, so we need to make sure that both symlinks and
copies give the same set of include 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.
>=20
Yes, maybe, this would work too.

So I take it as if you don't object if I create /usr/include/contrib
for now, and put ipfilter/ there, to deal with this PR?


Cheers,
--=20
Ruslan Ermilov		Sysadmin and DBA,
ru@sunbay.com		Sunbay Software AG,
ru@FreeBSD.org		FreeBSD committer,
+380.652.512.251	Simferopol, Ukraine

http://www.FreeBSD.org	The Power To Serve
http://www.oracle.com	Enabling The Information Age

--EXKGNeO8l0xGFBjy
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)

iD8DBQE+qNQ2Ukv4P6juNwoRAs/YAJ9GTr3UYRhXjVXYrxm8W3YKcD5O3gCggLqo
fjRScFiBl3prRyhIpTy02lw=
=JHem
-----END PGP SIGNATURE-----

--EXKGNeO8l0xGFBjy--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030425062247.GE32731>