Re: Fwd: [mico-devel] gcc 3.0.4
The upstream packaging for mico is fairly broken, they don't do library
naming properly for one thing, so it violates policy as it is. e.g.
mico-2.3.6.so instead of libmico.so.3.6.0. Also, nothing else currently
depends in mico in debian, I was thinking of just having the package
removed, unless someone wants to take it over and try to fix some of these
problems.
--
Stephen
On Tue, Feb 26, 2002 at 04:45:08PM +0100, Russell Coker wrote:
> I'm not the maintainer for mico any more, I haven't actually done anything
> with it apart from initially packaging it some years ago as part of my KDE
> packaging work. Stephen Crowley is the Debian maintainer now.
>
> On Tue, 26 Feb 2002 15:07, Christophe Prud'homme wrote:
> > I was wondering if this patch was applied to the gcc 3.0.4 package.
> > It seems that it would help compiling mico using 3.0.4
> >
> > Otherwise it seems that pr3145.patch solves most of the problems with mico
> > and since it is applied on debian packages that's cool !
> >
> > on a side note
> > what about mico 2.3.6 ? it has been out for quite some time now. Any plans
> > for 2.3.6 debian packages?
> > There is a also the micosec project htttp://www.micosec.org which is an
> > implementation of the CORBA security framework on top of MICO(2.3.6). It
> > might be interesting.
> >
> > Best regards
> > C.
Reply to: