I will not comment much on this. Just want to make sure people know about it. Read further to see why pidgin is no longer in the main stream of Slackware.
Recently on pidgin’s wiki they posted the following statement on Why Do we provide packages only for certain distributions and systems? As they put it. This is just a cut with the part pertaining to Slackware. I see no point in posting the full page here but will provide a link to the original they had up.
I will note that a Slackware user that frequents the ##slackware channel on freenode made a post to their mailing list asking them to change it. And the change was made. I will not speculate as to why they made the change as in their channel they defend their original statements.
From their page:
We have no developers using Slack, and furthermore, several of us actively dislike that distribution for its history of broken installs, as well as for its non-existent package management. You cannot create true packages for Slack.
At first glance one can get a lot of negative things from this. The catch is none of it is founded except that they have no developers using Slackware. The history of broken installs I would assume should refer to pidgin, as Slackware has a very good history. As for package management, Slackware has one. It simply does not do dependency checking leaving that for the user/admin. There are many reasons for this so I won’t touch on them here. A true package has been created and was created for some time. The creator of Slackware had maintained a package for GAIM for some time. So the main reason for the developers of pidgin to complain or even make this statement is just stupid.
As for Slackware’s stance on this, here is a cut from the changelog:
xap/pidgin-2.0.0-i486-2.tgz: Here's a little excerpt from: http://developer.pidgin.im/wiki/WhyPackagesExist "We have no developers using Slack, and furthermore, several of us actively dislike that distribution for its history of broken installs, as well as for its non-existant package management. You cannot create true packages for Slack." Well, I'm somewhat shocked by this, having never (to my knowledge) done anything to any of the former GAIM or Pidgin developers to make them mad at me, Slackware, or anyone on the Slackware team. I guess if they feel it's not possible to make a "true" Pidgin package for Slackware, there's no point in continuing to try. Having put out 7 security advisories on GAIM, I'm quite sure there will be less work here if Pidgin is not included. The Pidgin package has been moved to the "unsupported" directory. For the record, I do not actively dislike Pidgin or any of their developers, but I do plan to use Kopete from now on.
A copy of the original text can be found –> HERE