On 1 Feb 1999, Jim Pick wrote:
> > Ideally the devel GTK/etc -should- co-exist with the stable stuff, if it
> > doesn't then I think that is a serious problem. I can tolerate apps from
> > potato breaking left and right, but old apps from slink? Bleck.
>
> I'm becoming more convinced of the need
Jason Gunthorpe <[EMAIL PROTECTED]> writes:
> > > There are currently 72 things that link against imlib. I suspect that
> > > about half were linked with the 'old' imlib and half with the 'new' imlib.
> >
> > That's to be expected. The current situation demands that all those
> > apps should be
> > There is apparantly an EGCS patch called libapi, available in the
> > Debian egcs package, which is supposed to implement the above.
> > Adopting and improving this patch would definitely solve your GNOME
> > problems, Jim.
>
> Can you give us some pointers? This sounds like a good thing for
Hi!
> Jason Gunthorpe writes:
>> There is apparantly an EGCS patch called libapi, available in the
>> Debian egcs package, which is supposed to implement the above.
>> Adopting and improving this patch would definitely solve your
>> GNOME problems, Jim.
JG> Can you give us some pointers
On 1 Feb 1999, Jim Pick wrote:
> I'm not sure if you need to provide the original symbol - I think
> ld.so is smart enough to pull the appropriate symbols from the
> appropriate libraries (providing their symbol maps were set up
> correctly). There's at least 50 pages of documentation explaining
Jason Gunthorpe <[EMAIL PROTECTED]> writes:
> If glib, gtk, gnome, imlib, etc used versioned symbols then yes you
> -might- advoid this.
>
> -HOWEVER- my understanding how how versioned symbols would need to be
> implemented would make this pretty much impossible for a large portion of
> the lib
On 1 Feb 1999, Gordon Matzigkeit wrote:
> JG> Exactly what I mentioned during the libtool thread, however that
> JG> doesn't seem to be important. Ideally we could have a
> JG> /usr/lib/gnome-compat dir
>
> Bwahahahahah! :D
My thoughts exactly :> We are going to do this again when libstdc++
Hi!
> Jason Gunthorpe writes:
>> We could change the SONAME to designate the break in
>> compatibility. But then it wouldn't match upstream. It really
>> isn't the upstream maintainer's fault that we released one version
>> compiled against libglib 1.0, and one against libglib 1.1.
JG
On 1 Feb 1999, Jim Pick wrote:
> > > In fact, imlib is only being pulled in once. The problem is that glib is
> > > being pulled in twice (from libraries/binaries that were linked with
> >
> > The library that does this is imlib according to my investigation.
>
> Actually, it takes two librari
Jason Gunthorpe <[EMAIL PROTECTED]> writes:
> On 1 Feb 1999, Jim Pick wrote:
>
> > > libgdk-imlib1 in slink did not seem to depend on any glib, in potato it
> > > depends on a new and incompatible glib from potato BUT the soname was not
> > > changed. So the instant you install this new libgdk-i
On 1 Feb 1999, Jim Pick wrote:
> > libgdk-imlib1 in slink did not seem to depend on any glib, in potato it
> > depends on a new and incompatible glib from potato BUT the soname was not
> > changed. So the instant you install this new libgdk-imlib1 ~40 apps from
> > slink silently stop working!
>
Jason Gunthorpe <[EMAIL PROTECTED]> writes:
> On 1 Feb 1999, Jim Pick wrote:
>
> > > I somehow sense that slink/potato gtk/gnome is going to be painfull..
> >
> > I agree. I'm only planning to support Gnome 0.99.x/1.0 on potato.
>
> Oh, I was just reminded of this on the dpkg list.. The gtk (
Jason Gunthorpe <[EMAIL PROTECTED]> writes:
> On 1 Feb 1999, Jim Pick wrote:
>
> > > And note that it links to libglib twice. Turns out this is because there
> > > is two 'gdk-imlib1' packages with the same soname but linked against
> > > different versions of glib! By my count we have 72 differ
On 1 Feb 1999, Jim Pick wrote:
> > I somehow sense that slink/potato gtk/gnome is going to be painfull..
>
> I agree. I'm only planning to support Gnome 0.99.x/1.0 on potato.
Oh, I was just reminded of this on the dpkg list.. The gtk (gdk? I forget)
library packages have been internationalized
On 1 Feb 1999, Jim Pick wrote:
> > And note that it links to libglib twice. Turns out this is because there
> > is two 'gdk-imlib1' packages with the same soname but linked against
> > different versions of glib! By my count we have 72 different package that
> > depend on gdk-imlib1..
>
> I made
Jason Gunthorpe <[EMAIL PROTECTED]> writes:
> This is kinda neat, considering what we were talking about with libtool
> and all, examine this ldd output:
>
> Wakko{jgg}~/work/apt#ldd `which wmakerconf `
> libgdk_imlib.so.1 => /usr/lib/libgdk_imlib.so.1 (0x4000f000)
> libgtk.so.1
This is kinda neat, considering what we were talking about with libtool
and all, examine this ldd output:
Wakko{jgg}~/work/apt#ldd `which wmakerconf `
libgdk_imlib.so.1 => /usr/lib/libgdk_imlib.so.1 (0x4000f000)
libgtk.so.1 => /usr/lib/libgtk.so.1 (0x40031000)
libgdk.so.1
17 matches
Mail list logo
