The slackware package download is right here:

https://slackware.pkgs.org/14.2/sali...4-2gv.txz.html


Looks like it is supposed to run on 64-bit Slackware 14.2, which is what I am running.

I downloaded, and tried to install:

This is one reason why pkgs.org is not recommended. You're missing dependencies for that package... at least gtksourceview and possibly more. You need to verify you have all the required packages installed. There is a requires tab on the site that should provide you more info. But be warned, if you start mixing packages from different repos, you could run into issues where one program requires a certain dependency to be at a specific version, while another package requires that dependency to be at a different version.

This is why it is highly recommended to build your own programs after building all their dependencies.

EDIT: According to this, pluma is part of Mate, so it's possible it might require additional Mate dependencies. It might be best to build Mate from the Mate SlackBuild project.

pluma needs gtksourceview and pygtksourceview. You can build them from SlackBuilds available @ slackbuilds.org.

Bear in mind that if you grab a package from third party repository you have to take care of the dependencies yourself, beyond the packages included in a full Slackware installation.

PS bassmadrigal was faster.

PPS But you don't need the other Mate dependencies (I know that just because pluma is the default text editor in Slint).

PPPS I see that pygtksourceview is missing from the dependencies list on the the requires tab. But I confirm that it is needed (I just checked with "depfinder -p depfinder pluma-1.16.0-x86_64-2gv.txz").

My guess is that pygtksourceview is a build dependency only. The pluma package from the Salix repository run fine here without pygtksourceview installed. Also the dependencies listed in the Salix repo for pluma does not include pygtksourceview.

I am new to this.

Seems like pluma, and gedit, are more trouble than they are worth.

I am fine with vim for the command line, but would like something more graphical as well. I do not much care for the graphical vim.

Can anybody recommend a good Slackware XFCE editor?

There's lots of different editors. There was actually a thread recently that requested people's preferred editor.

http://www.linuxquestions.org/questi...es-4175603285/

Personally, I just use nano in the CLI and kate in the GUI (although, kate is KDE based).

There are many to choose from. I settled on Leafpad but it is just a personal preference on my part.

Oh, I see. From your other post on this subject and from using a search engine to investigate pluma and gedit I gather that you want syntax highlighting. Leafpad does not offer that

> There's lots of different editors.

Yes, but none of them will install on slackware without going through dependency hell.

I have tried: mousepad, nano, pico, kate, gedit, pluma, among others. Nothing works with just slackpkg installer. Going to slackbuild requires additional libraries, and the like.

I guess I should have gone with KDE instead of XFCE.

Of the ones you mentioned, nano, pico, and at least kate are included with a stock Slackware (possibly others, but I haven't looked into it).

slackpkg will only install packages from a standard Slackware mirror, and those should be installed by default with a full installation.

EDIT: And I believe none of those are standalone packages. I believe they're included in other packages. In that case, you'd need to use slackpkg file-search nano to search within the packages.
EDIT2: nano and kate are standalone packages, pico is part of the alpine package. All should be installed in a standard Slackware installation.

So Rich , that's probably why George didn't include pygtksourceview in the .dep. But as I wanted to rebuild myself everything included in the Slint repos I included it in the .dep in these repos. Maybe an overkill admittedly, but won't hurt.

Oh, and your post made me search for pluma in my IRC archive, and I see that as requested George removed the former dependency of pluma to mate-desktop when upgrading to mate 1.16.

First, as bassmadrigal pointed out there is no point using slackpkg to install already installed packages. But I now suspect that you didn't do a full Slackware installation, although this be strongly recommended for people not really acquainted to Slackware. This would highly reduce the dependency hell you are speaking about.

To get acquainted with Slackware, there are useful articles on http://docs.slackware.com

As already stated by others, another way to avoid dependency hell is sticking with the official Slackware repos (and maybe the few ones that clearly state the dependencies beyond a full Slackware installation, but then you still need to read this information to install these additional dependencies yourself), or build yourself packages from the stuff available @ slackbuids.org, reading and following the instructions in the README

Or, just install a Slackware derivative that provides automatic dependencies resolution like Salix or Slint. But even then, installing packages from random repositories will lead to the same dependency hell.

PS I see that you have posted a similar complaint here.

So as told already by Gordie there make a full Slackware installation instead of blaming a "dependency hell" that you created yourself. As the saying goes nemo auditur propriam turpitudinem allegans.

Oh, and before you ask why: http://docs.slackware.com/slackware:..._off_slackware

Thanks for the replies. I have given up on Slackware. Now using Calculate Linux.