On Wed, 22 Aug 2001, Martin Albert wrote:
> Tnx for your quick answer. As you didn't Cc the list neither do i now.
> Maybe you decide to forward.
Sorry, I was rushed, meant to CC to the list.
> Although i used every opportunity to talk about Free Software and Open
> Source Community that installation was simply more impressing ... ;-)
Yeah, it saves me time almost every single day, and only bites me in
the foot once a month (I run unstable), so all in all I'd count myself
a pretty satisfied apt/dselect user.
> (1) an as much as possible unmodified .orig source tree
> (2) static libs in -dev packages.
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.
> *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...
> What is xserver-ggi?
It is an X server that runs on GGI. Note there is also a branch of this
just recently started for libdirectfb, so the Debian packages for both will be
very similar. (Note I specifically did NOT say XFree86 server, because
it is not based at all on the XFree86 branch, hence it does not have a
XF86Config file, which causes a few problems with Debian's X system,
though less today than it did a year or so ago.)
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.
--
Brian
