On Wednesday, 22. August 2001 23:41, Brian S. Julin wrote:
> Do you really mean Debian wants every single LibGGI target, renderer,
> and extension lib all rolled into one .a? What do other packages
> that have plugins do for their -dev static libraries? I mean, a
> static (i.e., linked statically against libc) version of just the
> base libggi/libgii would be possible, and may even already work, but
> the modules cannot be static without building them in. I certainly
> hope that the latter is what the Debian policy really wants and not
> the former.
Not into one .a :)
Each -dev package MUST (that's the problem) have static libs
corresponding to the shared libs that are in the shared-libs-package.
> > *Bugs: libggidemos and svgalib4libggi collected lots and look bad.
>
> I'll look into those reports. I don't even know where the svgalib
> wrapper is kept these days...
I'll take care as soon as libggi_2.0.1 is out.
What is needed are demos, or i'ld have to rebuild the old package.
> Re: LibGGIMISC, it is not easy to move that back into the tree; it
> will have to be split as a package. And, I am actually about to add
> some more functions.
I will have to file an ITP (Intent to package) then to bugs.debian.org.
And i've got one more package ... ;)
>
> --
> Brian
Tnx, martin
