�Stefan van der Eijk� sagte am 2002-02-14 um 23:20:40 +0800 : > Is that based on any technical fact, or is it just "convenience" "lazyness"?
Depends, both is true I'd say. For one, it's lazyness. But on the other hand I don't think it's right that every gettext'able program (~70%?) should explicitly require such a base package. You may very well disagree with me on this one, but then I wonder why it would be wrong to also BuildRequires: gcc, bash, filesystem, rpm, rpm-build, perl.... IMO gettext is so basic, that it really fits in the above list, no? The same also applies to Requires:. Let's take the multi-gnome-terminal. Should I really add all these packages to the Requires? > for r in $(rpm -qR multi-gnome-terminal|grep -v =) ; do rpm -q --whatprovides $r ; >done | sort | uniq bash-2.05-15mdk common-licenses-1.0-5mdk db1-1.85-7mdk glibc-2.2.4-20mdk libaudiofile0-0.2.3-2mdk libesound0-0.2.23-1mdk libglade0-0.17-2mdk libglade-gnome0-0.17-2mdk libglib1.2-1.2.10-4mdk libgnome32-1.4.1.2-11mdk libgtk+1.2-1.2.10-18mdk libimlib1-1.9.11-8mdk libORBit0-0.5.13-1mdk libxml-1.8.16-1mdk XFree86-libs-4.1.0-22mdk zlib1-1.1.3-18mdk If not - which packages should *not* be added to the Requires: and why? Alexander Skwar -- How to quote: http://learn.to/quote (german) http://quote.6x.to (english) Homepage: http://www.iso-top.de | Jabber: [EMAIL PROTECTED] iso-top.de - Die g�nstige Art an Linux Distributionen zu kommen Uptime: 1 day 9 hours 42 minutes
