Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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
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?
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.
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 :-)
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
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)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
