Hi all,

I use SimplyMEPIS - a debian-based Linux. So far, I am quite happy with it.

I like to experiment to install new Linux programs in my box, which sometimes creates problems regarding dependency. Linux is a fast changing that everyday there will be always new version of packages. Problems are that a new package requires other packages of new version, while the other existing package requires the old version one. Forcing to install new package will uninstall the other old package.

I am not very sure how to handle this kind of problem. I get used to work in MS-Windows which the core update is not so often that this kind of problem is unnoticed when installing program.

I give you an illustration:
a. Currently I am happy with the existing Freemind program that requires libc6 (2.2.xxx)
b. I want to install the newest Beagle, which unfortunately requires libc6 (2.5.xxx)
c. Forcing to install newer Beagle will uninstall Freemind (and some other programs) that requires libc6 (2.2.xxxx)

One way is by upgrading Freemind as well, but as there are many other programs need to be updated as well, experimenting one new Beagle takes a lot time (not about installing the Beagle itself, but installing other programs as well) and the risks is quite high.

Is there a way to keep the old libc6 (2.2.xxx), while experimenting new Beagle (or other new program) is still carried on?

Any tips?

rgds,
antonius aji

Compile the software yourself from source code. It will be much easier than doing all of that stuff.

I am quite new-bie in Linux, and used to installing binary stuffs in Windows. So, I am not well prepared for compiling myself.

You mean that I have to compile the new software by myself?

As far as I guess, when I have to compile a software, it still requires some library (dependency) - it means that I have to installed the requirement first, before compiling. But, then when I installed the dependency - they remove the other packages. Is that correct?

I think I have to learn how to compile, any links where I can easily read? If possible, in debian environment.

rgds,
antonius aji

Sure - you can read Compiling programs from source - written by our very own jeremy

thank you! Who's Jeremy? (sorry for not knowing him)

ahaji, linux-rulz is LYING...well, for him it is true but for you it aint...well i had the same problem as u, and trust me, compiling source code will help 0.because when u install an rpm it tells u : libc++ is missing.so u know what to look for...when u compile from source it tells u make error 2...it's a difference.for me, 95% of the programs do not compile.and because i am a i cant debug or understand the errors...just get apt4rpm...trust me, i had and still have the same problem...the only way to really solve the dependency problem foreve is format / partition .I mean, i don't encourage u to do it, in fact DON"T DO IT, but just "waking" u to reality...sh*t happens...

Another solution is to simply use binaries compiled for your distro. That and compiling from source are the two safest options. Mucking around with other distros packages, even if in the same format, is going to lead you into problems.

I personally find compiling very easy. The configure script tells you what is missing, you install the headers for that package, and then compile. Of course, everyone is different.

linux, true although the ./configure script misses sometimes(tells u you dont have glib or something).it does tell u what to look for, but when ./configure works, and make gives you an error 2??don't tell me it doesnt happen, to me it happens a lot...that's the problem in fact...packages that ./configue script does not search for but are needed after all...

That's odd that that happens so often to you. I've only ever had it happen once with Transcode, and they fixed the configure script with the next release.

not the configure script
this usually works, but the make operation..i guess its about the automake and autoconf packages, which i did install and work though...dunno.

No, what I mean is if the configure script doesn't find everything, then it is a problem with the configure script. A lot of beta programs have this problem. For instance, transcode had a horrible configure script with their 0.6.x series, but once the program hit 1.0, the script now seems to work really well.

make errors, on the other hand, can be a pain, but as long as you have all of your headers installed, it normally works quite well (for me anyways).

linux i'm very glad for you...but very sad for me....anyways ill try more...there must be an answer....better ask my "2 problems" thread if you please...