GET HERE: aMSN 0.98SVN WITH Anti-Aliase Installer
 

Based DebianS (Ubuntu, others)
http://www.mediafire.com/?6l2dxbrbkmn

Command Line:

To Install: dpkg -i aMSN-0.98SVN-10-03-2008-tcl-tk8.6_libsnack-2.noarch.deb
To uninstall: dpkg -r amsn-0.98svn-10-03-2008-tcl

Based RedHat (rpm for mandriva, opensuse, redhat, others)
http://www.mediafire.com/?ogsjkwgyuuz

Command Line:

To Install: rpm -i aMSN-0.98SVN-10-03-2008-tcl-tk8.6_libsnack-2.noarch.rpm
To uninstall: rpm -e aMSN-0.98SVN-10-03-2008-tcl

To all system linux - Universal
http://www.mediafire.com/?xd3nbr6myxj

Command Line:
tar -xvzf aMSN-10-03-2008-tcl-tk8.6-installer.tar.gz
To Install: sh instalar.sh
To uninstall: sh uninstall.sh

Open aMSN, go in Account > preference > Advanced

Search by TLS, put /usr/local/amsn/share/amsn/tls1.50
Save and Close.

Enjoy it.

What does this give us over aMSN from a regular repo or from their site? Why are --no-deps and -force required to make this work? What can you tell us beyond the post above about these packages?

...and besides that, where do people go to for support if they find your package breaks things?

hey
 

the package is okey; make a test!!!

With all due respect for your work on these packages but your reply addresses none of the questions asked.

One of the basic rules is to only install packages from "trusted" vendors and people who know how to make packages (like the RPMForge people).
If you intended these packages as a spin-off from the official ones and you intend to continue producing or supporting them you best set up a permanent home for your packages (say Sourceforge or Savannah), and set up a bug tracker and a forum or mailing list for people to reach you.

With respect to your packages you should refer people to the aMSN Wiki that lists the steps to build the anti-aliased version of aMSN, list your dependencies and any steps that are different from the "official" build rules, provide the source packages and buildfiles and logs, sign packages with your GPG-key where possible and provide MD5 hashes for packages.

About using "--no-deps", that is a really bad move because it means you deliberately sidestep dependencies. That should *not* be used unless people are onehundred percent sure it doesn't result in crashes or other errors. If it's because of your package building skills then I suggest you learn from official packagers. Most of them have mailing lists you can ask questions on.


OTOH, if these packages are really one-offs and you do not intend to continue producing or supporting them you should aim for the support from the official aMSN developer or maintainer (which you should do anyway). Submit the packages and have him/her validate and list your packages on the official site.


If you are not willing to pursue any of these approaches, then what valid reasons do people have to trust your packages?

important
 

The problem is that much people complain of error in the compilation of aMSN, and this package here, is independent of the configuration of any system linux. It does not have any broken package, the command --force- -- nodeps can be removed. I wait to help in silence much people with these packages, that understand.

Ps: But if to indicate some dependence:
ln -s /usr/local/amsn/bin/wish8.6 /usr/bin/wish
ln -s /usr/local/amsn/bin/tclsh8.6 /usr/bin/tclsh

[QUOTE=unSpawn;3118840]With all due respect for your work on these packages but your reply addresses none of the questions asked.

One of the basic rules is to only install packages from "trusted" vendors and people who know how to make packages (like the RPMForge people).
If you intended these packages as a spin-off from the official ones and you intend to continue producing or supporting them you best set up a permanent home for your packages (say Sourceforge or Savannah), and set up a bug tracker and a forum or mailing list for people to reach you.
............

The aMSN Wiki outlines the procedure to build packages with anti-aliasing enabled. If people have trouble with aMSN at least they can contact the developer or maintainer. Since you clearly are not willing to support your own packages in any way and are not willing to validate or have them validated, I suggest people stay away from your handiwork. Case closed.