Re: Bug#534398: ITP: libposix -- unifed implementation of core functionality of all Unix systems

2009-06-24 Thread Steve Langasek
On Wed, Jun 24, 2009 at 09:02:26AM +1000, Aníbal Monsalve Salazar wrote: Package: wnpp Severity: wishlist Owner: Anibal Monsalve Salazar ani...@debian.org * Package name: libposix Why? This is a subset of the interfaces provided by glibc, which must be present on all systems. So it

Re: Bug#534398: ITP: libposix -- unifed implementation of core functionality of all Unix systems

2009-06-24 Thread Guus Sliepen
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

Re: Bug#534398: ITP: libposix -- unifed implementation of core functionality of all Unix systems

2009-06-24 Thread Bryan Donlan
On Wed, Jun 24, 2009 at 6:28 AM, Guus Sliepeng...@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

Re: Bug#534398: ITP: libposix -- unifed implementation of core functionality of all Unix systems

2009-06-24 Thread Guus Sliepen
On Wed, Jun 24, 2009 at 09:17:14AM -0400, Bryan Donlan wrote: Is libposix complete enough to link against for real programs yet? If not, why should it be included at this time? I agree that if the only thing that works at this moment is the simplest Hello world program, that it should not be

Re: Bug#534398: ITP: libposix -- unifed implementation of core functionality of all Unix systems

2009-06-24 Thread Bryan Donlan
On Wed, Jun 24, 2009 at 9:34 AM, Guus Sliepeng...@debian.org wrote: On Wed, Jun 24, 2009 at 09:17:14AM -0400, Bryan Donlan wrote: Is libposix complete enough to link against for real programs yet? If not, why should it be included at this time? I agree that if the only thing that works at

Re: Bug#534398: ITP: libposix -- unifed implementation of core functionality of all Unix systems

2009-06-24 Thread Michael Poole
Guus Sliepen writes: Moreover, can libposix and libc coexist in the same address space? What address space are you talking about? There is also dietlibc and uClibc, who can coexist with glibc. But applications can only link against one of them at the time of course. I suspect the concern

Re: Bug#534398: ITP: libposix -- unifed implementation of core functionality of all Unix systems

2009-06-24 Thread Cyril Brulebois
Guus Sliepen g...@debian.org (24/06/2009): On Wed, Jun 24, 2009 at 09:17:14AM -0400, Bryan Donlan wrote: Is libposix complete enough to link against for real programs yet? If not, why should it be included at this time? I agree that if the only thing that works at this moment is the

Re: Bug#534398: ITP: libposix -- unifed implementation of core functionality of all Unix systems

2009-06-24 Thread Steve Langasek
On Wed, Jun 24, 2009 at 12:28:24PM +0200, Guus Sliepen wrote: 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

Re: Bug#534398: ITP: libposix -- unifed implementation of core functionality of all Unix systems

2009-06-24 Thread Guus Sliepen
On Wed, Jun 24, 2009 at 05:47:16PM -0400, Steve Langasek wrote: Once libposix reaches maturity, I will certainly consider linking applications I wrote myself against libposix. Applications linked against it will probably use less memory Why would they use less memory? Since they don't

Re: Bug#534398: ITP: libposix -- unifed implementation of core functionality of all Unix systems

2009-06-24 Thread Bryan Donlan
On Wed, Jun 24, 2009 at 6:24 PM, Guus Sliepeng...@debian.org wrote: On Wed, Jun 24, 2009 at 05:47:16PM -0400, Steve Langasek wrote: Once libposix reaches maturity, I will certainly consider linking applications I wrote myself against libposix. Applications linked against it will probably

Re: Bug#534398: ITP: libposix -- unifed implementation of core functionality of all Unix systems

2009-06-24 Thread Pierre Habouzit
On Thu, Jun 25, 2009 at 12:24:40AM +0200, Guus Sliepen wrote: On Wed, Jun 24, 2009 at 05:47:16PM -0400, Steve Langasek wrote: Once libposix reaches maturity, I will certainly consider linking applications I wrote myself against libposix. Applications linked against it will probably use

Re: Bug#534398: ITP: libposix -- unifed implementation of core functionality of all Unix systems

2009-06-24 Thread Guus Sliepen
On Wed, Jun 24, 2009 at 06:33:44PM -0400, Bryan Donlan wrote: Why would they use less memory? Since they don't link against a large library. Granted, that is only a benefit if all running programs link against libposix instead of glibc. What makes you think libposix will be smaller?

Re: Bug#534398: ITP: libposix -- unifed implementation of core functionality of all Unix systems

2009-06-24 Thread Pierre Habouzit
On Thu, Jun 25, 2009 at 12:41:43AM +0200, Pierre Habouzit wrote: On Thu, Jun 25, 2009 at 12:24:40AM +0200, Guus Sliepen wrote: On Wed, Jun 24, 2009 at 05:47:16PM -0400, Steve Langasek wrote: Once libposix reaches maturity, I will certainly consider linking applications I wrote myself

Re: Bug#534398: ITP: libposix -- unifed implementation of core functionality of all Unix systems

2009-06-24 Thread Pierre Habouzit
On Thu, Jun 25, 2009 at 12:54:35AM +0200, Guus Sliepen wrote: On Wed, Jun 24, 2009 at 06:33:44PM -0400, Bryan Donlan wrote: Why would they use less memory? Since they don't link against a large library. Granted, that is only a benefit if all running programs link against

Re: Bug#534398: ITP: libposix -- unifed implementation of core functionality of all Unix systems

2009-06-24 Thread Samuel Thibault
Pierre Habouzit, le Thu 25 Jun 2009 00:41:43 +0200, a écrit : Why would they use less memory? Since they don't link against a large library. Which is a ridiculous argument given what the S in .so means. And linking against a 100MB library will generally _not_ eat 100MB memory during

Bug#534398: ITP: libposix -- unifed implementation of core functionality of all Unix systems

2009-06-23 Thread Aníbal Monsalve Salazar
Package: wnpp Severity: wishlist Owner: Anibal Monsalve Salazar ani...@debian.org * Package name: libposix Version : 0 Upstream Author : Henrique Almeida hda...@gmail.com * URL : http://libposix.sourceforge.net/ * License : See below Programming Lang: C