On Tue, Jan 14, 2003 at 11:41:12AM +0900, ISHIKAWA Mutsumi scrawled: > >>>>> In <[🔎] 20030114013550.GA5772@trinity.unimelb.edu.au> > >>>>> Daniel Stone <dstone@trinity.unimelb.edu.au> wrote: > >> > How about xft1 ? > >> > >> Xft is not built at all. > > Humm, some applications uses Xft1 so we will need libXft.so.1 > for compatibility. We need oldlibs/libxft1 package. I think it should be all or nothing - either we have both xft1 and xft2 internal, or external, not one or the other. > >> splitting xlibs per-library locally in my tree, but that's > >> > >> going to take a couple of days yet to track down where every > >> > >> header and manpage should go (sigh). > >> > > >> > Ahh, I understand. So, we will provide individual package per > >> > libraries? (For example xlibx11 will provide libX11.so and related > >> > files, xlibxie will provide) > > >> AIUI, the rough plan is to have one package per shared library (libx11, > >> libxpm4, etc), xlibs-static and xlibs-data. I'm unsure as to how the > >> packages should be named though: I honestly don't see the need for the > >> 'x' prefix, except as some ancient packaging artifact that's no longer > >> relevant to the real world. > >> > >> * debian/control: > >> + Split xlibmesa a la 4.2.1-5 - xlibmesa4-gl, xlibmesa4-gl-dbg, > >> xlibmesa4-gl-dev, xlibmesa4-glu, xlibmesa4-glu-dbg, xlibmesa4-glu-dev, > >> and xlibmesa4-dri. The first three contain libGL, the next three libGLU, > >> and the latter the DRI modules. > > 4.2.1-4pre5v1 provides xlibmesa-gl-dev, xlibmesa-glu-dev and > xlibosmesa-dev. Yes, xoslibmesa-dev is also provided in my package. > So, If xlibmesa4-gl-dev, xlibmesa4-glu-dev and xlibosmesa4-dev will > not co-exists with current (4.2.1-4pre5v1 and probably 4.2.1-5) > xlibmesa-gl-dev, xlibmesa4-glu-dev and xlibosmesa-dev, I think better > `4' would be dropped from their names. Right, good point. Thanks for the pick-up. :) I'll rename the -dev packages to have the soname dropped. > >> + Split xlibs a la Branden's Great Leap Forward - every package has its own > >> library. So, the new packages are: libx11, libxpm4, libxt6, libxmu6, > >> libxmuu1, libice6, libsm6, libxext6, libxi6, libxp6, libxrender1, > >> libxrandr2, libxtrap6, libxtst6, libxrx6 and libxcursor1; all of these > >> packages also have a -dbg and -dev package (the soname is removed for > >> the -dev package). Locale data and other architecture-independent > >> stuff has been moved to xlibs-data; static-only libraries are in > >> xlibs-static. > > Cool :-) > > Perhaps we need dummy xlibs package (it depends these > library packages) to migrate from old environment. I've been thinking about this, yeah. Thanks a lot for your feedback; I'll have to check out your packages sometime soon, but at the moment I have too much other stuff on my plate. :( Cheers! :) d -- Daniel Stone <dstone@trinity.unimelb.edu.au> Developer, Trinity College, University of Melbourne
Attachment:
pgpdsFM_gEGQs.pgp
Description: PGP signature