Date: Tue, 22 Aug 2000 17:25:50 +0100 From: Paul Richards <paul@originative.co.uk> To: Jeroen Ruigrok van der Werven <jruigrok@via-net-works.nl> Cc: Ollivier Robert <roberto@eurocontrol.fr>, FreeBSD Current Users' list <freebsd-current@FreeBSD.ORG>, green@FreeBSD.ORG Subject: Re: make buildworld br0ken in libutil Message-ID: <39A2A98E.EC1D33C4@originative.co.uk> References: <20000822172846.A76574@caerdonn.eurocontrol.fr> <20000822175309.U86398@lucifer.bart.nl> <20000822175438.B76789@caerdonn.eurocontrol.fr> <20000822180037.B28016@lucifer.bart.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
Jeroen Ruigrok van der Werven wrote: > > -On [20000822 17:55], Ollivier Robert (roberto@eurocontrol.fr) wrote: > >According to Jeroen Ruigrok van der Werven: > >> Alternatively the sentiment just rose why we couldn't just collapse the > >> crypt/hash functions of libcrypt into libc. > >> > >> It would make sense. > > > >It would make even make more sense to convince the other BSD to do the same > >(haven't checked recently what they do) and do the merge. > > I very much agree. > > Would it be sensible for the regular cypherpunks to discuss this with > the NetBSD and OpenBSD brothers? > > Otherwise I would be willing to open this discussion on the appropriate > lists. Is there any current policy on what libc is? It certainly isn't "libc" as required by C and hasn't been for almost ever but there needs to be some rational to its existence otherwise why not fold everything into libc and not bother with any other libraries! A growing libc makes static binaries grow and makes it more difficult to strip out unneeded functionality from a minimalist system install. I'd been inclined to try and move things the other way and strip stuff out of libc into separate libraries but that's obviously not in vogue at the moment. Why does crypt need to be in libc? Not even a significant fraction of applications need crypt? Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?39A2A98E.EC1D33C4>