On Sunday 25 March 2001 12:56, Stefan van der Eijk wrote:
| Nicolas,
|
| > Therefore, there's stg that I find a little puzzling : why is it that
| > every time a new release (ie MDK 8) is showing, all the RPM packages
| > suddendly requires dependencies that weren't needed with the latest
| > "official" release (MDK 7.2 in this case) ?
|
| Mdk 8.0 has glibc 2.2, while 7.2 has an older one. They aren't
| compatible, that's why rpm is complaining. If you want to install the
| mdk 8.0 openssl on you're 7.2 machine, then you'll also need to upgrade
| glibc, which will then force you to upgrade most other applications as
| well --> something you could consider to be a complete OS upgrade.
LM 7.2 was binary compatible with LM 7.0 and 7.1
I effectively was using Cooker's binary RPMs for upgrading my LM 7.0 until
October 2000 - when LM 7.2 was released (and I obtained set of LM 7.2 CDs,
thanks to one kind man on this list)
|
| > Let's take an example : I wanted to try to install the latest openssl
| > 0.9.6 from cooker instead of the 0.9.5 currently in mdk 7.2.
Pls be careful when upgrading from OpenSSL 0.9.5 to 0.9.6
They are *binary incompatible*. It is problem with OpenSSL library, not
Cooker.
You will need to recompile apps depending on OpenSSL in that case.
(for example, kdelibs and kdebase ...)
| > I got a 'GLIBC 2.2' needed, but I don't understand why. Obviously
| > openssl consists of libraries, so there shouldn't be real dependencies
| > on glibc 2.2 (I know open ssl 0.9.6 compiles even xith the old libc5),
| > so why do I get this kind of dependencies ?
|
| Because with mdk 8.0 they were compiled against glibc 2.2.
|
| > Is that the standard mandrake RPM policy to add require for the latest
| > GLIBC (instead of requiring for example GLIBC >= 2.0) ? Do you use some
| > kind of predifine macros to build your RPMs that tend to add these
| > constraints ? Or could I just use '--nodeps' to force insalling those
| > RPMs ?
|
The best I can recommend to you here is to grab latest SRPM from Cooker, and
--rebuild it on LM 7.2 box.
I did it already for KDE 2.1 and Gnome 1.4.
So,, I continue to run LM 7.2 and most *important* for me apps on current
Cooker level.
| --nodeps will install the rpm, but you won't be able to use it, as it
| won't run with the old glibc. Actually, you could take the openssl
| src.rpm and rebuild it on your system (glibc 2.0?) and the install the
| resulting rpm. That will (probably) work.
|
| > I had a similar example hen I wanted to try to install xmms 1.4.1 over
| > mdk 7.2 -> missing libstdc++ dependency.
| >
for xmms - look at mandrake-devel/unsupported.
You can find there XF 4.0.2-11, 4.0.3, KDE 2.1, xmms and some other nice apps.
| > All in all, I find it very annoying to be forced to upgrade the whole
| > system to install only a few recent packages (not that I don't like
| > upgrading to the latest MDK distrib, it's just I'd like to do it 'step
| > by step' before resintalling the whole distrib).
|
you should try mandrake-devel/unsupported than.
Check list of available Cooker mirrors, go to mandrake-devel directory, than
unsupported.
| Nobody forced you todo anything. Mandrake is working on their next
| product, which has the latest stuff in it. You're experiencing some
| problems because the latest stuff is built on glibc 2.2 (I guess this is
| where innovation hurts). But, since the sources are also available, feel
| free to recompile them (src.rp,) for your system, you have the freedom
| to do so.
I still, personally, wonder what is so grreat in glibc 2.2
And IMHO if they break compatibility they should change major version number.
Like, name it glibc 3.0
KDE 3.0 (which is supposed to be binary incompatible with KDE 2.0) goes
exactly in this way.
Then, everybody knows that dot-zero version can be buggy (and binary
incompatible, if major version changed)
I belive it will fix a lot of issues for many people.
| > While RPM was meant to be a format to ease packages update,
| > it seems
| > there's a trend with various distrib where upgrading some packages with
| > those from a more recent distrib is impossible (but not due to missing
| > libraries functionnalities, due to the way the RPM files are build).
I have heard that Debian has very flexible packaging.
Haven't tested it though.
| > Am I all wrong ?
I guess the most important is to *include* dependencies.
Then you can take control of update process..
Otherwise, you can miss something, and will not know what you are missing and
why program is not working.
|
| > Thanks for any explanations on this subject (and congratulations to all
| > the Mandrake people for such great distribs !)
I hope checking mandrake-devel/unsupported can fix a lot of your problems.
|
| Stefan
--
Vadim Plessky
http://kde2.newmail.ru (English)
http://kde2.newmail.ru/index_rus.html (Russian)
Do you have Arial font installed? Just test it!
http://kde2.newmail.ru/font_test_arial.html
