Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×
Upgrades

Journal Scott Lockwood's Journal: Pidgin disrespects Slackware: Is Slack still important? 1

In the latest changelog for Slackware Current development, is the following entry:

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.

Now, while I myself cut my teeth on slackware in 1993, I haven't actively used it for years, since adapting Ubuntu as my distro of choice. I don't think that declining market share of Slack justifies such a crappy comment from the Pidgin team however, and I'm glad to see that the page the comment was made on has been changed to reflect a far more professional attitude. However, it does beg the question: Is Slackware still relevant? Is it time for Slackware to go the way of SLS and Yggdrasil?

This discussion has been archived. No new comments can be posted.

Pidgin disrespects Slackware: Is Slack still important?

Comments Filter:

Work is the crab grass in the lawn of life. -- Schulz

Working...