Re: Bug#534398: ITP: libposix -- unifed implementation of core functionality of all Unix systems
On Wed, Jun 24, 2009 at 6:28 AM, Guus Sliepen<guus@debian.org> wrote:
> On Wed, Jun 24, 2009 at 11:03:41AM +0100, Steve Langasek wrote:
>
>> On Wed, Jun 24, 2009 at 09:02:26AM +1000, Aníbal Monsalve Salazar wrote:
>> > * Package name : libposix
>>
>> Why?
>>
>> This is a subset of the interfaces provided by glibc, which must be present
>> on all systems. So it would be stupid for any package in Debian to link
>> against libposix instead of just using libc. Why do we want a library in
>> Debian that no packages should depend on?
>
> Just see it as dash vs. bash. Once libposix reaches maturity, I will certainly
> consider linking applications I wrote myself against libposix. Applications
> linked against it will probably use less memory and cannot inadvertently use
> glibc extensions. This will make it easier to port those applications, and will
> also make it easier to run things on embedded platforms.
Is libposix complete enough to link against for real programs yet? If
not, why should it be included at this time?
Moreover, can libposix and libc coexist in the same address space? If
not, all of debian's existing libraries will be incompatible with it.
It seems like the sort of thing that you might want to build an entire
distro against, or a custom/development build against, but not just
some programs in a distro...
Reply to: