Bug 175359 - Pango has a wrong build requirement on cairo instead of cairo-devel
Summary: Pango has a wrong build requirement on cairo instead of cairo-devel
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: pango
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-12-09 13:11 UTC by Matthias Saou
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2005-12-19 17:36:51 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Matthias Saou 2005-12-09 13:11:00 UTC
In the current FC devel pango, the line :

BuildRequires: cairo >= %{cairo_version}

Needs to be changed to :

BuildRequires: cairo-devel >= %{cairo_version}

Otherwise the package might get built without cairo support, and gtk2
will then refuse to rebuild.
(note that the requirement in the pango-devel sub-package is correct)

Comment 1 Matthias Saou 2005-12-09 13:16:57 UTC
Note also that in the spec file, this :

Prereq: libXrender, libX11, libXext, libXft

Is not needed, as those library dependencies will get picked up automatically
by rpm. Since there is no specific version requirement (unlike freetype, gtk2
and cairo here).

One more note, these lines are redundant and the first could be removed :
Prereq: freetype >= %{freetype_version}
Requires: freetype >= %{freetype_version}
(since no %pre scriplet requires stuff contained in freetype)

Maybe you'd be interested in a global spec file patch to clean it all up?

Comment 2 Matthias Clasen 2005-12-09 14:56:31 UTC
Sure, a patch would be great. I think the versioned freetype req may be there to
avoid some bugs in older versions, though

Comment 3 Matthias Saou 2005-12-14 10:32:38 UTC
While looking some more at the spec file, I started wondering about if there
could be a way to simplify the whole $host and -32/-64 binary install process.
The part that bothers me most is that you end up with a pretty much useless
shell script in %post, since it tests a hardcoded string...

It would be much cleaner to get the "final" $host as an rpm macro in order to
just use it everywhere in the spec (including %post and %files).

Another quick suggestion :
%if %{_lib} == lib64
/usr/bin/pango-querymodules-64
%else
/usr/bin/pango-querymodules-32
%endif

This way, once again, there is no test against the (now) hardcoded $host
made in %post, but instead the correct script is directly called.

Comments? Should I go ahead and try and implement those changes?

Comment 4 Matthias Clasen 2005-12-19 17:36:51 UTC
I fixed the cairo buildrequires

Comment 5 Matthias Saou 2005-12-19 17:48:39 UTC
OK, I guess you're not too keen taking the risk to break the whole 32/64bit
script thing, which I perfectly understand :-)


Note You need to log in before you can comment on or make changes to this bug.