Re: libmqueue: worth packaging?
On Mon, Jul 19, 2004 at 03:34:22PM +0900, GOTO Masanori wrote:
> Hi,
>
> At Sun, 18 Jul 2004 18:42:57 +0200,
> Mattia Dongili wrote:
> > as per subject I'm interested in packaging libmqueue [1], but the
> > author says it's been included in glibc 2.3.4 and thus no more actively
> > maintained as a separate package.
>
> I think the opinion of the arthor is quite sane. It should be part of
> C library.
>
> POSIX mqueue is integrated in kernel 2.6.6 or 2.6.7 (in Apr 2004) and
> it needs glibc 2.3.4, cvs version Apr 2004. Yeah, at least Jakub
> already implemented his original version in Dec 1999, when I got the
> patch from him.
Right, and since our kernel (I checked i386 config only but I suppose
CONFIG_POSIX_MQUEUE has the same setting everywehre else) come with
CONFIG_POSIX_MQUEUE=y I though it could be nice to have necessary
libraries to support and use the feature
> > Now my question is mainly if we'll have glibc 2.3.4 (and thus mqueue.h)
> > in sarge, if not it would be probably useful packaging mqueue library
[...]
> At least I don't update glibc until sarge is released. This means
> that mqueue library is not available in sarge. So I think it's good
> idea to package libmqueue if you want to get it in sarge. But once
yes, and I also doubt sarge will ever have a glibc upgrade in future
revisions :)
> sarge is released, I update glibc to the latest cvs (This is one
> reason why I would like to release sarge as soon as we can. Our glibc
> becomes obsolete).
>
> I leave the decision to you. You can freely package libmqueue, but
> it's meaningful until sarge is released.
of course. Leaving sarge without mqueue support is such a pity I'll
package it :) I'll ITP it, let's see if talking about it in d-devel will
add more opinions.
Thanks
--
mattia
:wq!
Reply to: