LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   I think the Slackware community would like this file manager (https://www.linuxquestions.org/questions/slackware-14/i-think-the-slackware-community-would-like-this-file-manager-4175670264/)

dugan 02-25-2020 02:19 PM

I think the Slackware community would like this file manager
 
It's written in BASH, for one thing. Surprisingly small codebase.

https://github.com/dylanaraps/fff

volkerdi 02-25-2020 02:25 PM

That looks pretty cool, but to be honest I think the name alone will keep it out of Slackware...

JWJones 02-25-2020 02:31 PM

He should have went with Freaking Fast File-Manager...

hitest 02-25-2020 02:38 PM

It does look good, man. Maybe a package re-name?

ReFracture 02-25-2020 03:04 PM

Ya know.. reading the page, being already fully aware of what this program is called.. somehow didn't stop me from laughing out loud when reading the first bullet point.

volkerdi 02-25-2020 03:49 PM

Quote:

Originally Posted by hitest (Post 6094189)
It does look good, man. Maybe a package re-name?

I'm not one to decide to rename a package from what upstream calls it. Probably SBo is the place for it.

andigena 02-25-2020 03:55 PM

Quote:

Originally Posted by volkerdi (Post 6094185)
That looks pretty cool, but to be honest I think the name alone will keep it out of Slackware...

Do you have specific policies pertaining to this or are you just excluding it because the name is dumb?

Either way, I wouldn't consider it useful enough to be included by default. Just curious.

volkerdi 02-25-2020 04:00 PM

Quote:

Originally Posted by andigena (Post 6094209)
Do you have specific policies pertaining to this or are you just excluding it because the name is dumb?

There's no specific policy, and I have previously included things covered by the WTFPL, but a package name is a little bit more public-facing.

Quote:

Either way, I wouldn't consider it useful enough to be included by default. Just curious.
I'm not sure it's useful enough to be included by default either, but the name certainly doesn't help. And if it were to be included, the stigma of the name would rub off on us at least a bit.

hitest 02-25-2020 04:01 PM

Quote:

Originally Posted by volkerdi (Post 6094206)
I'm not one to decide to rename a package from what upstream calls it. Probably SBo is the place for it.

I did not mean to imply that you should rename it, Patrick. Sorry for the miscommunication on my part. My suggestion was for the package creator.

volkerdi 02-25-2020 04:03 PM

Quote:

Originally Posted by hitest (Post 6094212)
I did not mean to imply that you should rename it, Patrick. Sorry for the miscommunication on my part. My suggestion was for the package creator.

Ah, OK. Point taken, and no offense taken either :)

andigena 02-25-2020 04:12 PM

Quote:

Originally Posted by volkerdi (Post 6094211)
There's no specific policy, and I have previously included things covered by the WTFPL, but a package name is a little bit more public-facing.



I'm not sure it's useful enough to be included by default either, but the name certainly doesn't help. And if it were to be included, the stigma of the name would rub off on us at least a bit.

That's understandable, though I think a distribution which shows random whimsical messages when the user logs in and whose name is itself a Church of the SubGenius reference can be afforded a bit of leeway in the realm of unprofessional package names. ;)

volkerdi 02-25-2020 04:32 PM

Quote:

Originally Posted by andigena (Post 6094216)
That's understandable, though I think a distribution which shows random whimsical messages when the user logs in and whose name is itself a Church of the SubGenius reference can be afforded a bit of leeway in the realm of unprofessional package names. ;)

Yeah, that's been a can of worms over the years. Back when Morse Telecommunications was Slackware's publisher, Michael R. Johnston insisted on calling it "Slackware Professional Linux" to defuse it a bit (and I couldn't disagree). In retrospect, "Professional Linux" itself would have been a better name in terms of dressing for success.

I guess my point is we've already got too much of that sort of baggage and don't need more.

andigena 02-25-2020 04:36 PM

Quote:

Originally Posted by volkerdi (Post 6094220)
Yeah, that's been a can of worms over the years. Back when Morse Telecommunications was Slackware's publisher, Michael R. Johnston insisted on calling it "Slackware Professional Linux" to defuse it a bit (and I couldn't disagree). In retrospect, "Professional Linux" itself would have been a better name in terms of dressing for success.

I guess my point is we've already got too much of that sort of baggage and don't need more.

I much prefer "Slackware" myself; it's more memorable and rolls off the tongue nicely. Certainly not terribly appealing to business users, though!

tramtrist 02-25-2020 04:39 PM

Confession.. I rolled a Slackware server years ago in a work environment. Years later when I had moved on to another group... someone was probing around the groups regarding what that particular server was floating around out there.. finally when I said it was a "Slackware" server running some services, I swear a bunch of the people in the department thought it was a virus and mildy freaked out on me... Apparently anything ending in 'ware' is now associated with Malware..............
True story.

I'm only 37 years old but man.. did I feel old that day.

ReFracture 02-25-2020 04:42 PM

Fortune has at times been entertaining.. but honestly at a certain point I removed the executable permission from it.


All times are GMT -5. The time now is 06:11 AM.