|
From: Juan T. <to...@us...> - 2001-04-04 08:50:52
|
Both problems probably relate to the fact that I am building the rpm packages in my Debian machine, and I can't even test them afterwards. Both dpkg and rpm create dependencies automatically checking the libraries to which the final binary is linked to. That is probably why you are seing alsa as a requirement, since that is what I have installed on my machine. The db2 requirement I am a bit more surprised about. My own compilation failed to complete until I had it installed, and I assure you I don't use any function from that library directly. I guess it is a new gnome dependency, but the autoconf macros have not updated to reflect the fact. Perhaps if I installed db3 installed of db2? Is the third version standard on Redhat installations? In any case, the proper solution to the problem would be to "outsource" redhat packages creation, since my machine is probably not the best place to do those Regards, Juan. On Tue, Apr 03, 2001 at 11:24:46PM -0400, Dmitri Pogosyan wrote: > Dear Juan, > > Thanks for etherape, I'm enjoying it very much ! > Regarding lates 0.5.7 rpm package I have some problems: > > 1. Why does precompiled binary rpm require libdb2.so.2, which is > a part of development package db2-devel ? > > 2. Is it possible to create rpm compiled without alsa support ? I use > just OSS > for sound :( > > Best regards, Dmitri Pogosyan > > -- > CITA, University of Toronto pog...@ci... > 60. St. George Street tel: 1-416-978-7616 (o) > Toronto, Ontario, M5S 3H8 tel: 1-416-466-4028 (h) > Canada fax: 1-416-978-3921 > > -- Etherape, a graphical network monitor modeled after etherman http://etherape.sourceforge.net/ |