On Sun, 22 Jun 2008 16:18:14 +0300 Adrian Bunk <[EMAIL PROTECTED]> wrote:
> A tool is never a replacement for a brain. ;-) > > I do not doubt that the library has a dependency on libglide. > > But why is display-glide not only in an extra package but also built > into the library? > > Especially since the this was not done in 2.2.1-5 but is done > in 2.2.2-1? I probably should have clarified the glide situation. In 2.2.1-5 libggi was build depending on libglide3-dev which caused the glide display target not to build since it needs libglide2, and so the glide target was basically non existent in 2.2.1-5, this was rectified in 2.2.2-1 and hence the extra dependency. If you look at the other targets, the same thing is present, i.e libggi2 depends on libaa1 etc. With respect as to why it's in both the shared display target and the main library, basically most of the display targets are considered 'builtin', (this includes glide), and so are available without the external shared libraries, hence the linking against the static display targets. The reason the external shared display targets exists are for people the use them externally, or to use with libggi itself if they are not considered 'builtin'. I hope this clarifies everything, just say if it doesn't. Please close the bug if it does, and you're happy, so we can avoid a bug opening/closing war. ;) Regards, Bradley Smith -- Bradley Smith <[EMAIL PROTECTED]> GPG: 0xC718D347
signature.asc
Description: PGP signature
