Bug 172 - too many requirements for minicom build
Summary: too many requirements for minicom build
Status: CLOSED FIXED
Alias: None
Product: Sisyphus
Classification: Development
Component: rpm-utils (show other bugs)
Version: unstable
Hardware: all Linux
: P4 minor
Assignee: placeholder@altlinux.org
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-11-21 23:57 MSK by imz
Modified: 2003-08-25 15:18 MSD (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description imz 2001-11-21 23:57:27 MSK 
buildreq for minicom-2.00.0-alt4 generates an unreasonably long list of requirements: 
packagereq: 
building requires list:                                                                                             bison cups gimp-print kernel22-source kernel24-source libncurses-devel libtermcap-devel pcmcia-cs

The only really used packages are the two lib*-devel.
All others are probably detected during the execution of ./configure.
---

---
I have three ideas of possible solutions (all of them are not good):

1. exclude files that are commonly used in autotools\' tests from the set of files that are important for detecting the packages;

2. do not trace ./configure and its child processes;

3. put %configure to another section of the spec-file (not %build, but %prep), so that one can first execute %prep without tracing, and then trace the %build stage.
Comment 1 Dmitry V. Levin 2002-09-28 21:24:01 MSD 
Seems to be fixed (i.e. was minicom package problem):

now buildreq minicom produces:

# Automatically added by buildreq on Sat Sep 28 2002
BuildRequires: libtinfo-devel
Comment 2 Dmitry V. Levin 2002-09-28 21:24:01 MSD 
Seems to be fixed (i.e. was minicom package problem):

now buildreq minicom produces:

# Automatically added by buildreq on Sat Sep 28 2002
BuildRequires: libtinfo-devel