Mailinglist Archive: opensuse (3349 mails)

< Previous Next >
Re: [SLE] Installing other distros RPM packages?
  • From: Sid Boyce <sboyce@xxxxxxxxxxxxxxxx>
  • Date: Mon, 09 May 2005 21:53:58 +0100
  • Message-id: <427FCDE6.1030600@xxxxxxxxxxxxxxxx>
Hylton Conacher (ZR1HPC) wrote:
I have a working SuSE 9.0 system which I use. All of the packages are off the 9.0 CD's and I 'prefer' to only use SuSE compiled RPM's as then I know files are going to be installed in the correct place, wherever that may be. From time to time I see software package updates, either on CD or the web but they are for another distro ie Mandrake and perhaps others.

Is it possible to use those RPM's via YaST and still have them install in the correct SuSE locations or as it might be a Mandrake RPM it will install in locations Mandrake would have.

Basically the question revolves around location, location, location. Being in the right place at the right time, is crucial to property and most other things and I wonder if the installed location is as important or different between distros using the same package format?

As both Mandravia and SuSE subscribe to the FHStandard can the above assumption be made?

In the good old days, you could grab a rpm of deb package and install it on any other distro, not so now. The FHS allows quite a bit, it's more a guide to how the filesystem should be set up rather than a cast iron guide to where people install stuff or what features the include, e.g /opt and /usr/local/bin are there in Mandriva, both empty. When you look into it, you can see the pain it causes if you are a developer, you must build separate packages for each distro unless you use static linking.
The Connectiva packages used to be compatible with SuSE, checking the Mandriva LE 2005 (obviously old Mandrake), everything seems to go in /usr, e.g all the kde binaries are in /usr/bin and the libraries in /usr/lib. The Mandriva stuff should still work on SuSE providing a particular app doesn't depend on something not compiled into the SuSE libraries or compiled with different libs.... e.g..
barrabas:/ftp/May05 # rpm -ivh /media/cdrom/media/main3/cooledit-3.17.7-8mdk.i586.rpm
warning: /media/cdrom/media/main3/cooledit-3.17.7-8mdk.i586.rpm: V3 DSA signature: NOKEY, key ID 70771ff3
error: Failed dependencies:
pythonlib is needed by cooledit-3.17.7-8mdk
libCw1 = 3.17.7-8mdk is needed by cooledit-3.17.7-8mdk is needed by cooledit-3.17.7-8mdk
The Mandriva package does not include libCw1, on SuSE 9.3 cooledit built from sources and made into an rpm with checkinstall includes libCw1 and doesn't depend on pythonlib - both apps have the same appearance.
Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot
Retired IBM Mainframes and Sun Servers Tech Support Specialist
Microsoft Windows Free Zone - Linux for all Computing Tasks

< Previous Next >