Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 121962 - automake-1.4 is marked as requirement everytime even if it isn't needed
automake-1.4 is marked as requirement everytime even if it isn't needed
Product: Fedora
Classification: Fedora
Component: fontconfig (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Owen Taylor
Depends On:
Blocks: 125755
  Show dependency treegraph
Reported: 2004-04-29 07:33 EDT by Robert Scheck
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-08-03 19:01:28 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Robert Scheck 2004-04-29 07:33:58 EDT
Description of problem:
automake 1.4 is everytime marked as a requirement even it isn't 
needed (so automake is only used at s390 systems for disabling
some documentation).

Version-Release number of selected component (if applicable):

How reproducible & Steps to Reproduce:
Everytime, rebuild fontconfig on a non-s390 system and you see, that 
automake isn't used and also shouldn't be marked as a requirement.
I personally use the patch below, which works for me.
Actual results:
--- fontconfig.spec        2004-04-19 18:03:52.000000000 +0200
+++ fontconfig.spec.rsc    2004-04-29 13:18:02.000000000 +0200
@@ -39,8 +39,9 @@
 BuildRequires: expat-devel
 BuildRequires: perl
 # For nodocs patch
+%if %{disable_docs}
 BuildRequires: /usr/bin/automake-1.4
 PreReq: freetype >= %{freetype_version}


Expected results:
A solution like mine or better ;-)
Comment 1 Owen Taylor 2004-08-03 19:01:28 EDT
I don't think a conditionalized dependency on architecture
makes sense, so I'm not going to fix this. (Though I'm going
to try removing the disabling of docs on s390 in the next build
which would make this irrelevant.)

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