Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 6 Oct 2003 14:53:01 +0300
From:      Ruslan Ermilov <ru@freebsd.org>
To:        Stijn Hoop <stijn@win.tue.nl>
Cc:        Mark Murray <mark@grondar.org>
Subject:   Re: docs/50349: make release fails with NO_OPENSSH and ! NOKERBEROS
Message-ID:  <20031006115301.GA52277@sunbay.com>
In-Reply-To: <20031006102006.GA76051@pcwin002.win.tue.nl>
References:  <20031004190337.GB94900@sunbay.com> <200310041930.h94JUCYJ065458@grimreaper.grondar.org> <20031005041432.GC9334@electra.cse.Buffalo.EDU> <20031005184629.GB37106@sunbay.com> <20031006102006.GA76051@pcwin002.win.tue.nl>

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

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

On Mon, Oct 06, 2003 at 12:20:06PM +0200, Stijn Hoop wrote:
> On Sun, Oct 05, 2003 at 09:46:29PM +0300, Ruslan Ermilov wrote:
> > On Sun, Oct 05, 2003 at 12:14:32AM -0400, Ken Smith wrote:
> > > On Sat, Oct 04, 2003 at 08:30:12PM +0100, Mark Murray wrote:
> > >=20
> > > > The crypto stuff in nicely separated out, and I wouldn't mind seeing
> > > > further separation (dev tools, LPR, sendmail, etc) done as separate=
ly
> > > > installable components, similar to the crypto install.
> > >=20
> > > A current interest is having some sort of binary updates system
> > > in place.  Everyone I talk to about the various issues, projects in
> > > motion, etc. say this further separation of stuff would help that
> > > effort a LOT.
> > >=20
> > The (crypto) stuff is already well separated, it's just that
> > we don't want to further complicate release/Makefile to
> > account for the NOCRYPT option -- it's much easier to remove
> > the unneeded bits after release is rolled.
>=20
> What about this then:
>=20
> [stijn@pcwin002] <~> ldd /usr/bin/fetch=20
> /usr/bin/fetch:
>         libfetch.so.3 =3D> /usr/lib/libfetch.so.3 (0x28076000)
>         libssl.so.3 =3D> /usr/lib/libssl.so.3 (0x28083000)
>         libcrypto.so.3 =3D> /lib/libcrypto.so.3 (0x280b5000)
>         libc.so.5 =3D> /lib/libc.so.5 (0x281c3000)
>=20
> It seems to me that a release build with crypto and installed without
> will miss /usr/bin/fetch, or will it simply not work? Haven't tried yet,
> but I was just wondering.
>=20
cd /usr/src/release && make -V FIXCRYPTO

You should see the usr.bin/fetch there; this means that the release.3
stage of "make release" recompiles it without crypto support and puts
the crypto-free binary into the "base" distribution.


Cheers,
--=20
Ruslan Ermilov		Sysadmin and DBA,
ru@sunbay.com		Sunbay Software Ltd,
ru@FreeBSD.org		FreeBSD committer

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

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

iD8DBQE/gVedUkv4P6juNwoRArdRAJwMa0D830NHUBPvch3tYZfJ0BP0EQCggh3O
O3MwgMNe2uPfuXylC+Fm/6Y=
=JqIf
-----END PGP SIGNATURE-----

--uAKRQypu60I7Lcqm--



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