|
Pages: [1]
|
 |
|
|
Author
|
Topic: RPM versus Source Packages (Read 841 times)
|
Vern Heesch
Administrator
Newbie
Posts: 22
|
Mandriva is a RPM based distro and therefore only RPM's should be used on the system. Installing packages from source can have undesired results on a RPM based distro.
A Mandriva RPM is designed to install packages in certain places, with certain file names. These locations will ALWAYS differ when installed by source. Also some of the packages file names can differ as well. These two differences can cause havoc with your system.
Why would it cause havoc? Let's say you have already installed package foo.rpm previously and now you install a newer version of the app by source. You now have two separate installations of the same app on the system, and both are now located in different places. Most things installed from source end up in /usr/local/ and this IS NOT where a Mandriva RPM installs too.
Ok, that not enough to convince you to avoid installing apps from source? How about this... say you did install the app 'foo' from source and now want to install a Mandriva RPM that has as a dependency of 'foo'. Since you had installed 'foo' from source, the Mandriva RPM will not see it because it wasn't installed where the Mandriva RPM would have put it. This situation would cause Mandriva to install the foo.rpm which again gives you two separate versions installed on the same system.
As you can see, mixing source and RPM's on a RPM based distro is not really wise. There will be times that you want an app installed that Mandriva does not have. In these cases it's best to make an RPM of the app and install that instead. Creating RPM's can be rather difficult depending on the app and it's requirements, but I would suggest trying it, or finding someone who may be willing to try and create a RPM for you.
The Mandriva RPM howto is located here: http://qa.mandriva.com/twiki/bin/view/Main/RpmHowTo
Bottom line to this: ONLY INSTALL PACKAGES BY SOURCE IF YOU CANNOT FIND THE APP IN RPM FORMAT AND/OR YOU CANNOT GET OR BUILD A RPM OF IT. A clean, organized system of RPM installs only will leave the system in the condition/state it's meant to be in.
|
|
|
|
« Last Edit: August 06, 2005, 11:37:14 AM by Hawkwind »
|
Logged
|
|
|
|
TuGGer
Newbie
Posts: 1
|
"Mandriva is a RPM based distro and therefore only RPM's should be used on the system."
I've used Mandrake (ahem Mandriva) since LM 8.0, and it's the first time I've heard this caution. Certainly I would use an rpm whenever one is available, but I would not hesitate in using a 'source' package to get the cutting-edge-all-bells-and-whistles functions usually included in newer versions. One caution, and it should be self-evident: remove the current rpm first, if you plan to upgrade.
A case in point: Mandrake spreads its Postgresql files all over the place in unconventional locations (as noted in this post). This makes it very, very, very messy when you need to add some custom features to a configuration like Apache + PHP + Postgresql. I know: I had to finally dump the mdk rpms and custom-build from scratch. That experience taught me a valuable lesson: if you want 'MS-type' functionality, stick to the rpms. However, if you need to build something that you need, source is the only way to go. That experience introduced me to the incredible power of Linux, and the friendly functionality of Mandrake that can co-exist with source-built packages. Most of my system is source add-ons with LM 9.1 - it runs beautifully.
"This situation would cause Mandriva to install the foo.rpm which again gives you two separate versions installed on the same system."
Yup. Done that - but a simple uninstall of the older rpm will take care of most problems. (I have had an older OpenOffice LM version rpm and the current OO 2.0 on the same machine. I just updated the links to point to the newer version, then uninstalled the older rpm.) I regularly update OO this way, and have had no problems whatsover.
I think the bottom line is this: if you don't want/need to learn more about Linux, stick with rpms. However, if you would like to learn a little, try a source package that is not listed in the rpm. (use Kpackage - it's your friend to find out where all the files are). Then as you feel more adventurous and gain more skills try progressively harder progs.
Have fun learning - tinker a bit - it ain't M$, ya know :>
From an OlderNewbie
TuGGer
|
|
|
|
|
Logged
|
|
|
|
|
Pages: [1]
|
|
|
|
|
