linking statically against dietlibc: a blocker?

[Enrico Scholz]

denis at poolshark.org (Denis Leroy) writes:

> I'm concerned with the complexity involved in introducing multiple
> competing C libraries in FE (duplicated security audit efforts),

Affected packages are very small programs which are using almost only
simple syscall wrappers from libc. See [1] for a full analysis of freedt.


> a choice that to me should be left to the upstream project rather
> than to the packager. Also I don't buy the efficiency argument:

See [1] and [2] for some numbers.




Enrico

Footnotes: 
[1]  https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=176582

[2]  https://www.redhat.com/archives/fedora-extras-list/2006-February/msg01827.html
     https://www.redhat.com/archives/fedora-extras-list/2006-February/msg01842.html