Re: UPDATE: graphics/cairo and graphics/py-cairo

[Eric Faurot]

On 11/24/05, Aleksander Piotrowski [EMAIL PROTECTED] wrote:
 Eric Faurot [EMAIL PROTECTED] wrote:

  I understand. I am using this patch locally and I have xchat,
  firefox 1.5rc3 working well. I can make a full package build,
  run make newlib-depends-check and see what happens.
  Would that help? Anyway, we can leavecairo like this for now.
  It simply adds a useless lib dependency, but nothing harmful
  as far as I can tell.
 
  However py-gtk2 really requires the updated py-cairo
  (for pycairo.pc)

 Yeah, but 150+ ports are more important that one py-gtk2 port.

Sorry, it was not clear: the py-cairo update does not depend on the
cairo update. I was suggesting to update py-cairo and py-gtk2 but
leave cairo untouched for now.

 And yes, as you are updating port that has lots of dependant ports, you
 should, erm, you have to run full pkg build to be sure that everything is OK
 after that change.

I'll do that.

Eric.

Re: UPDATE: graphics/cairo and graphics/py-cairo

[Christian Weisgerber]

Eric Faurot [EMAIL PROTECTED] wrote:

 Remove the incorrect -lfreetype flag in cairo.pc. This is IMHO a
 mistake in cairo distribution because one can link against libcairo
 without linking against libfreetype.  The -L/usr/X11R6/lib flag is

Have you talked to the cairo people about this?

 left to allow ports like pango to detect cairo correctly (pango, for
 example). I wonder if it is really the way to go and I am starting to
 think that the whole pkg-config concept is actually broken. Anyway,
 the change affects all ports that use pkg-config to link against cairo
 but do not explicitly need freetype. Their WANTLIB might need to be
 fixed (remove freetype).

Seeing that it might again affect ~150 ports, I'm reluctant about
this change.

-- 
Christian naddy Weisgerber  [EMAIL PROTECTED]

Re: UPDATE: graphics/cairo and graphics/py-cairo

[Aleksander Piotrowski]

Eric Faurot [EMAIL PROTECTED] wrote:

  Seeing that it might again affect ~150 ports, I'm reluctant about
  this change.
 
 I understand. I am using this patch locally and I have xchat,
 firefox 1.5rc3 working well. I can make a full package build,
 run make newlib-depends-check and see what happens.
 Would that help? Anyway, we can leavecairo like this for now.
 It simply adds a useless lib dependency, but nothing harmful
 as far as I can tell.
 
 However py-gtk2 really requires the updated py-cairo
 (for pycairo.pc)

Yeah, but 150+ ports are more important that one py-gtk2 port.

And yes, as you are updating port that has lots of dependant ports, you
should, erm, you have to run full pkg build to be sure that everything is OK
after that change.

Alek
-- 
From: Przemyslaw Frasunek
Subject: OpenBSD rootkit?
To: [EMAIL PROTECTED]
 -- http://www.monkey.org/openbsd/archive/tech/0207/msg00123.html

Re: UPDATE: graphics/cairo and graphics/py-cairo

[Eric Faurot]

Hi

py-cairo.diff was broken, sorry. Here is a better one.

Eric.


py-cairo.diff
Description: Binary data

UPDATE: graphics/cairo and graphics/py-cairo

[Eric Faurot]

Hi,

Here are two patches for cairo and py-cairo.

For cairo:

Remove the incorrect -lfreetype flag in cairo.pc. This is IMHO a
mistake in cairo distribution because one can link against libcairo
without linking against libfreetype.  The -L/usr/X11R6/lib flag is
left to allow ports like pango to detect cairo correctly (pango, for
example). I wonder if it is really the way to go and I am starting to
think that the whole pkg-config concept is actually broken. Anyway,
the change affects all ports that use pkg-config to link against cairo
but do not explicitly need freetype. Their WANTLIB might need to be
fixed (remove freetype).

For py-cairo
py-cairo does not depend on py-gtk2 anymore, since py-gtk2 will
include cairo support. pycairo.h is moved into
${LOCALBASE}/include/cairo and the missing pycairo.pc is added.

Does that make sense?

Eric.


cairo.diff
Description: Binary data


py-cairo.diff
Description: Binary data