yast dosn't react

smajser · 04-09-2006, 07:00 AM

i downloade this rpm(BitTorrent-4.0.2-3.1.i586.rpm) and i am trying to install it with yast from root but when i clik on extract packege with yast it wont even open. have i downloade wrong rpm?
i am using suse 9.1

Mega Man X · 04-09-2006, 07:16 AM

Use the command line instead. It will give you a better output for errors:

rpm -Uvh BitTorrent-4.0.2-3.1.i586.rpm

Read this too:

Useful thread and information about installing programs.

coolb · 04-09-2006, 07:22 AM

Quote:

Originally Posted by smajser

i downloade this rpm(BitTorrent-4.0.2-3.1.i586.rpm) and i am trying to install it with yast from root but when i clik on extract packege with yast it wont even open. have i downloade wrong rpm?
i am using suse 9.1

RPMs can be a real pain, why not build from source?

XavierP · 04-09-2006, 07:41 AM

Because if you build from source on Suse, YAST will not be aware of the program/libraries. Which means that it will always complain about it being a missing dependency. And Yast won't auto-update it like the rest of the programs.

coolb · 04-09-2006, 07:43 AM

Quote:

Originally Posted by XavierP

Because if you build from source on Suse, YAST will not be aware of the program/libraries. Which means that it will always complain about it being a missing dependency. And Yast won't auto-update it like the rest of the programs.

o ok, I havent used SuSE so I dident know. but still building from source is better :-)

Mega Man X · 04-09-2006, 07:50 AM

Quote:

Originally Posted by coolb

o ok, I havent used SuSE so I dident know. but still building from source is better :-)

Could you define better? Usually, building from source is helpful if

- you want to compile the source with very specific optimizations for you hardware or

- add/remove things from the source code. The way most peoples build source (./configure, make && make install), will hardly make any improvement to the performance. And you will still need to deal with dependencies.

It's always better to stick with packages or package managements native for you distribution, unless you want to do one of the things I said above

coolb · 04-09-2006, 09:14 AM

Quote:

Originally Posted by Mega Man X

Could you define better? Usually, building from source is helpful if

- you want to compile the source with very specific optimizations for you hardware or

- add/remove things from the source code. The way most peoples build source (./configure, make && make install), will hardly make any improvement to the performance. And you will still need to deal with dependencies.

It's always better to stick with packages or package managements native for you distribution, unless you want to do one of the things I said above

I had a url that explained this umm... let me check for it.
Cant find it but let me add..

1. compiled for the architecture and optimizations(like you said)
2. enhanced performance and customization
3. less dependency issues(some cases, some contain the needed libs etc)

btw binarys are normally the dependency problems.