Stefan van der Eijk ([EMAIL PROTECTED]) wrote: > Han wrote: >>dam's ([EMAIL PROTECTED]) wrote:
>>> I'm going to include it, but why did you removed this buildrequires : >>> #esound-devel ORBit-devel imlib-devel gtk+-devel >> Well quite easy: irssi is a console tool. > It's not that easy... Have you tried building it without those packages > installed on your system? If that works, the BuildRequires may be removed. I hope you don't mind that I use common sense when I build a package instead off blind guessing. But for your concern I tried some other, more sensible, steps to figure out the possible dependencies: It would be a shame if my irssi build would miss some nice options so I read the ./configure --help|less, the install guide and the OpenBSD port build instructions. And not to my surprise: no such options. Nowhere nada niente noppes. As a matter of fact I don't use irssi on my Mandrake desktop but only on my OpenBSD firewall. Which has no X-support whatsoever. The dependeciessnippet from that port: BUILD_DEPENDS= msgfmt::devel/gettext LIB_DEPENDS= glib.1.2::devel/glib Ok now lets check my system: [~]$ rpm -qa|grep esound-devel [~]$ rpm -qa|grep ORBit-devel [~]$ rpm -qa|grep imlib-devel [~]$ rpm -qa|grep gtk+-devel Here ya go. No such packages. Well now we want to know why those dependencies were in it in the first place right. Well that is easy explained by the historical way irssi was developped: It did have a gtk frontend but that was a long time ago: Can't find the info on the website but rpm is a wonderfull tool: * Tue Dec 05 2000 Daouda Lo <[EMAIL PROTECTED]> 0.7.97-1mdk - update - big changes in spec (cleanup, GTK/GNOME support dropped by the author) - fix ncurses build dependencies - new description - libproplist isn't needed anymore (irssi ship his own conf lib) OMG have all those package maintainer simply missed that. :D Cya, Han.
