SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've been a user of swish-e for many years. It's used on my desktop so has no external exposure - I hope.
It's not had an update since April 2009 - version 2.4.7. It's never been in slackBuilds.org. It's web page has been archived. The last entry in the E-mail Discussion List was from 2008. So no longer supported and probably nobody else uses swish-e except me. I find it useful.
The zlib (1.2.11) update on Slackware stable broke swish-e. Zlib introduced a new function called uncompress2 which conflicted with the swish-e internal uncompress2. I was heartbroken.
It was a simple fix to swish-e to rename it's internal uncompress2 to uncompressS. So I've now got swish-e back up and running.
Not sure how to move forward -
stick with swish-e and fix as and when it needs fixing
move on to something similar that is supported.
Last edited by aikempshall; 11-20-2018 at 04:58 AM.
Reason: implicit mention of swish-e
^ Actually SWISH++ doesn't seem to be more maintained than Swish-e.
According to https://sourceforge.net/projects/swi...swishplusplus/, last update was on 2008-01-25.
But maybe there is no uncompress2 conflict with that version, I don't know...
Have found a "later" version of swish-e on github from 2016. I think it was set up to address a memory fault in swish-e. Though I didn't suffer from the memory fault on my desktop it did occur consistently when I was running in virtualbox.
I did drop an email to the person that set up swish-e on github, but have had no reply.
I've cloned swish-e locally. I could push my patch up to github, though I doubt it will get very far if no one's maintaining it. I could fork.
I'm having trouble reaching the github address for swish-e with a browser. Could l0f4r0 post a git-cloneable address, please. I have a weak spot for snapshots from old, abandoned projects. Or any sort of link/attachment to the sources for swish-e.
I'm having trouble reaching the github address for swish-e with a browser. Could l0f4r0 post a git-cloneable address, please. I have a weak spot for snapshots from old, abandoned projects. Or any sort of link/attachment to the sources for swish-e.
For you to clone with HTTPS: https://github.com/uddhab/swish-e.git
But please note that I don't know anything about SWISH-E (I was just trying to determine the "later version of swish-e on github from 2016" that aikempshall was speaking about) so I cannot be sure this address is reliable and is the most relevant starting point...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.