Mark Murray wrote:

> > Why does crypt need to be in libc? Not even a significant fraction of
> > applications need crypt?
> Goes for very many libc components. Quite a lot of userland needs libcrypt
> (not much as a proportion, but a non-insignificant number).

This runs counter to my gut instinct of development which is to
modularise code. Modularisation is accepted as a goal in all other areas
of the tree it doesn't make sense to me why that thinking is being put
to one side when it comes to the libraries.

Maybe this should move to arch because I guess I'd like to see a actual
design discussion as to why the current thinking is to collapse
libraries into libc rather than to actually go the other way and
modularise the code.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to