Re: [Cooker] Re: [CHRPM] fribidi-0.9.0-2mdk

2001-10-01 Thread R.I.P. Deaddog

On Mon, Oct 01, 2001 at 02:27:46PM +1000, Geoffrey Lee wrote:
  The problem is, for pango to link with external fribidi library, fribidi
  must be linked against glib 1.3.x in turn. Another choice is to upgrade
  pango to newest version, which contains a mini fribidi library inside, so
  that the external fribidi library can be removed completely from cooker.
 
 Well I prefer not to link with glib 1.3.6 unless absolutely necessary ...

Hmmm, maybe it's better to leave the trouble for Pablo . LOL

Abel




Re: [Cooker] Re: [CHRPM] fribidi-0.9.0-2mdk

2001-10-01 Thread Pablo Saratxaga

Kaixo!

On Mon, Oct 01, 2001 at 02:58:33PM +0800, R.I.P. Deaddog wrote:
 On Mon, Oct 01, 2001 at 02:27:46PM +1000, Geoffrey Lee wrote:
   The problem is, for pango to link with external fribidi library, fribidi
   must be linked against glib 1.3.x in turn. Another choice is to upgrade
   pango to newest version, which contains a mini fribidi library inside, so
   that the external fribidi library can be removed completely from cooker.
  
  Well I prefer not to link with glib 1.3.6 unless absolutely necessary ...
 
 Hmmm, maybe it's better to leave the trouble for Pablo . LOL

I don't think that pango requiring glib 1.3.* is much of a problem; it
won't be widely deployed and used on systems without it.

Now, if the next version allows compiling without it, then that would
solve your problem when it will be included in cooker (I saw the announce of
the new version, but the 8.1 was already in deep freeze).
Note however that the pre-compiled rpm package of pango will still link
with glib 1.3.*, as it is needed by the gtk+ 1.3.* lib (and that is it's main
reason of including it: testing the new gtk (and it may be already useful
for some people)).
Now a recompilation with a one line change in the spec file shouldn't be
a problem

 
 Abel

-- 
Ki ça vos våye bén,
Pablo Saratxaga

http://www.srtxg.easynet.be/PGP Key available, key ID: 0x8F0E4975




Re: [Cooker] Re: [CHRPM] fribidi-0.9.0-2mdk

2001-10-01 Thread R.I.P. Deaddog

On Mon, 1 Oct 2001, Pablo Saratxaga wrote:

 I don't think that pango requiring glib 1.3.* is much of a problem; it
 won't be widely deployed and used on systems without it.

 Now, if the next version allows compiling without it, then that would
 solve your problem when it will be included in cooker (I saw the announce of
 the new version, but the 8.1 was already in deep freeze).
 Note however that the pre-compiled rpm package of pango will still link
 with glib 1.3.*, as it is needed by the gtk+ 1.3.* lib (and that is it's main
 reason of including it: testing the new gtk (and it may be already useful
 for some people)).

Hmmm, can pango be linked without glib 1.3.x at all!?

Anyway it is discussing whether fribidi must be linked with glib 1.3.x;
currently it must be the case (otherwise pango refuses to use external
fribidi library). But for newer pango, it is another story; pango 0.20
(dunno for older versions) includes a mini-fribidi library, so that
external fribidi is just optional. Actually including external fribidi
won't work without patching; filed a bug report+patch in bugzilla, but
nobody has taken care of it yet.

Abel





Re: [Cooker] Re: [CHRPM] fribidi-0.9.0-2mdk

2001-09-30 Thread Geoffrey Lee

 *** may want to edit the glib-config-2.0 script: /usr/bin/glib-config-2.0
 checking for glib-config... /usr/bin/glib-config
 checking for GLIB - version = 1.2.0... yes
 
 so glib 1.3 doesn't seem to be accepted by firbidi because it uses the 
 old /usr/bin/glib-config-2.0 script.
 
 [stefan@bi SPECS]$ glib-config-2.0
 glib-config-2.0 is no longer supported. Please use pkg-config instead
 
 So fribidi goes ahead and uses glib-1.2... Any idea's on how to get it 
 to compile with glib-2.0? Hack in support for pkg-config?



_Must_ we compile this with glib 2.0 ...? It's still development stuff ...

- G.





Re: [Cooker] Re: [CHRPM] fribidi-0.9.0-2mdk

2001-09-30 Thread R.I.P. Deaddog

On Mon, Oct 01, 2001 at 12:25:03PM +0800, Stefan van der Eijk wrote:
 
 Stefan, for pango to use this external fribidi library, fribidi must be
 explicitly linked against glib 1.3 (not only glib).. can this be
 changed?
 
 I'm trying to... but on bi (mandrake compile host) I'm getting the 
 following output:
[.]
 checking for glib-config-2.0... /usr/bin/glib-config-2.0
 checking for GLIB - version = 1.3.1... no
[.]
 [stefan@bi SPECS]$ glib-config-2.0
 glib-config-2.0 is no longer supported. Please use pkg-config instead

Oh sorry I forgot to warn against this... the old fribidi 0.9.0 won't
work anymore with glib = 1.3.6, since glib-config-2.0 is discontinued
for glib = 1.3.6. But the fribidi in CVS, after some tweak, works
perfectly. I have created an RPM, placed in

http://linux-hall.com/~maddog/files/gnome2/mdk-SRPMS/fribidi-0.9.0-2.0mdk.src.rpm

Can you take a look at it?

Abel

PS You can go to fribidi.sourceforge.net to have a look.




Re: [Cooker] Re: [CHRPM] fribidi-0.9.0-2mdk

2001-09-30 Thread R.I.P. Deaddog

On Mon, Oct 01, 2001 at 01:45:11PM +1000, Geoffrey Lee wrote:
  
  So fribidi goes ahead and uses glib-1.2... Any idea's on how to get it 
  to compile with glib-2.0? Hack in support for pkg-config?
 
 _Must_ we compile this with glib 2.0 ...? It's still development stuff ...

The problem is, for pango to link with external fribidi library, fribidi
must be linked against glib 1.3.x in turn. Another choice is to upgrade
pango to newest version, which contains a mini fribidi library inside, so
that the external fribidi library can be removed completely from cooker.
I have almost finished creating all these RPMs  but that's another
story.

Abel