Amsn96 For Suse10.2

Hello; I am new on this forum. I am in no way a technician but still think some others may have a use for my findings over last several tense hours.

aMSN96 was unwilling to install in SUSE10.2 Linux.

Googling (in fact, Metaseeking) angrily after every error/missing message during install attempts, also per each subsequent new RPM, I found and downloaded 4 missing RPMs which had to be installed FIRST and moreover, in a firm ORDER.

Herebelow, the list of total 6 RPMs by which I finally (of course with old aMSN95 switched OFF) got the thingamy on board & working; I do not know the differences with No.95 yet, but working is working.

So: the numbers I put in front of each name, are not in the original names and neither are they to be found on the Web.

1 tclxml-3.1-1.guru.suse102.i686.rpm

2 tclxml-devel-3.1-1.guru.suse102.i686.rpm

3 tcldom-3.1-2.guru.suse102.i686.rpm

4 tclsoap-1.6.7-2.guru.suse102.noarch.rpm

5 amsn-0.96-0.2.guru.suse102.i686.rpm

6 amsn-plugins-0.96-0.2.guru.suse102.i686.rpm

Note: after the install, aMSN location in program list at "internet / chat" now stands immediately added, so no more (like with No.95) under "more programs".

Hello; I am new on this forum. I am in no way a technician but still think some others may have a use for my findings over last several tense hours.

aMSN96 was unwilling to install in SUSE10.2 Linux.

Googling (in fact, Metaseeking) angrily after every error/missing message during install attempts, also per each subsequent new RPM, I found and downloaded 4 missing RPMs which had to be installed FIRST and moreover, in a firm ORDER.

Herebelow, the list of total 6 RPMs by which I finally (of course with old aMSN95 switched OFF) got the thingamy on board & working; I do not know the differences with No.95 yet, but working is working.

So: the numbers I put in front of each name, are not in the original names and neither are they to be found on the Web.

1 tclxml-3.1-1.guru.suse102.i686.rpm

2 tclxml-devel-3.1-1.guru.suse102.i686.rpm

3 tcldom-3.1-2.guru.suse102.i686.rpm

4 tclsoap-1.6.7-2.guru.suse102.noarch.rpm

5 amsn-0.96-0.2.guru.suse102.i686.rpm

6 amsn-plugins-0.96-0.2.guru.suse102.i686.rpm

Note: after the install, aMSN location in program list at "internet / chat" now stands immediately added, so no more (like with No.95) under "more programs".
[/b]

It's best to install with a package manager instead of individual rpms from the web. Whichever package manager you are using (i.e. yast or zen or smart etc.) you can add the packman and guru repositories, update your existing repositories, and then you should have no trouble installing amsn. I updated my amsn this morning with no problems.

You can find the most important extra repositories listed here: Additional Yast Repositories

but still think some others may have a use for my findings over last several tense hours.[/b]

Thanks for sharing your solution. As noted, a Package Manager to manage such 3rd party applications would have taken the pain away (and done this semi-automatically), but still, the information in your post is definitely useful for those who have not learned the benefits of a Package Manager. Thanks for sharing.

I remember, before I started using a Software Package Manager to install my 3rd party multimedia (and other favourite 3rd party apps) I used to maintain a list of something in the order of 100 3rd party applications, that I would install with every new SuSE release. ie. I would download the rpms individually. Then I would install them one by one. It was slow (very very slow), but it worked.

@oldcpu:
Thank you for your extensive comments, which to my regret I fail to understand.

Right now I am completing a bug report to aMSN, which opened automatically at my attempt to click (dropout menu, account) "preferences".

Thank you for your extensive comments, which to my regret I fail to understand.[/b]

OK, let me try again.

Please read post#9 in this thread I am going to quote:
http://forums.suselinuxsupport.de/index.ph...=complications#

As you have discovered, sometimes when you try to install application-a, you first need applications-b, c and d. But to install application-c, you need application g, e, f, ... etc ... etc .... And they all have to be installed in a correct order, with the correct versions, which is not written down anywhere easy to find.

Hence users like you, and like me, used to keep lists of the applications, and the specific order of installation required, in order to successfully install an application.

However, by using a software package manager (designed specifically for semi-automating this process) this checking is done automatically, and one can install in minutes, what could take hours of trial and error to do before. For example, the application "Smart", and the application "Synaptic/apt" can do this.

Is that more clear? Or have I missed your point?

OK, let me try again.

Please read post#9 in this thread I am going to quote:
http://forums.suselinuxsupport.de/index.ph...=complications#

As you have discovered, sometimes when you try to install application-a, you first need applications-b, c and d. But to install application-c, you need application g, e, f, ... etc ... etc .... And they all have to be installed in a correct order, with the correct versions, which is not written down anywhere easy to find.

Hence users like you, and like me, used to keep lists of the applications, and the specific order of installation required, in order to successfully install an application.

However, by using a software package manager (designed specifically for semi-automating this process) this checking is done automatically, and one can install in minutes, what could take hours of trial and error to do before. For example, the application "Smart", and the application "Synaptic/apt" can do this.

Is that more clear? Or have I missed your point?
[/b]

Thanks, will try and read more about "package manager".