How about "Patrick's Patreon hits 30-300K a month" and then he adopts apt-get. You raise money for something prior to delivering the deliverables right?

1 members found this post helpful.

I am can-tan-ker-ous because I keep replying to this thread, and I know I shouldn't.

2 members found this post helpful.

That sounds great. They really need and want big fonts. The system has 4GB of DDR2 RAM so it should be able to install it. eZoom sounds like what they need. Thanks for the information!

We do love to get pulled into train wreck threads...

2 members found this post helpful.

So ok only thing that legit just irks me about Slackware is the installation options i.e. Menu and Expert - exact same thing ... Maybe one should be removed or again the very least have either Menu or Expert output changed to terse during install -- that is all

1 members found this post helpful.

So he is serving 15 years to life --- so ... in 2023 will he be eligible for parole or something?

Yes, March 2023 according to Wikipedia. Geez, that time has gone quick.

Back in 2006, I was a user of (and advocate for) v3 of his filesystem. After he agreed to plead guilty, I switched to XFS.

well...I just had a big slug of vodka with mango juice so I'll wade in, TL;DR more or less as it were...

Exhibit A:
if the dependency tree extends past 2 or 3 levels, even an automatic tool will tend to fuck that up. I give up past level 2 usually and then and see if Slackware already has software plenty good enough for the task. I know we all have our favorite "app" but consider: Slackware has a ton of useful software already included. Do I really need to add more?

Exhibit B:
on 2 boxes with Slackware64-Current multlib, I can go from power on -> runlevel 3 -> startx -> KDE/Plasma5 in 12 sec plus/minus 2 sec if I am quick on the user/password. Why would I want to monkey with thet kind of performance?
Ryzen 7 3800X, 16 GB RAM, NVME pci-e 4.0
Ryzen 9 3900X, 32 GB RAM, NVME pci-e 4.0

Exhibit C:
Plain text configuration files; XML etc is ok, NOT BINARY. Any distro or software project that thinks different is run by fucking idiots. Not everything needs to be stuck in a binary blob or database. I'm looking at you, pulseaudio...

Now enough of this nonsense. time to fire up Steam and turn Slackware into a high performance gaming console! WOOOO!

2 members found this post helpful.

I bet not for him though .

I never advocated anything, I did use ReiserFS around that time but I was trying different types to see what would fit / suite me. I recall though I had bad luck with ReiserFS v3, and so I switched to JFS , which worked great and still works great - along with XFS. I wonder though if v3 even receives any updates, I know JFS hasn't been receiving updates since 2011, so I am reluctantly thinking about moving away from JFS. Hopefully XFS doesn't go the same way.

Also at this point, I wonder who if anyone even uses Reiser4 - supposedly someone is actually maintaining it - but yea it will never be adopted to the main kernel - and I would imagine the userbase (again if there even is one); will be so low that perhaps whoever is maintaining it will throw in the towel.

Yeah, I found XFS to be great for physical disks... but there aren't many of those left in my life these days. I'm almost 100% SSD now, and so I've switched to ext4 because that was the concensus among the articles I consulted about it. It seems to be the most stable and best supported.
Yeah, not being in the kernel would have hurt its chances badly. The same can be said for OSS4.

Awesome idea. Shall we consider the following:
1) Once Patrick's Patreon reaches 30k/month, we can start asking for the adoption of apt-get
2) Once it reaches 300k/month, Patrick has to add apt-get to Slackware

everyone's happy?

1 members found this post helpful.

So... 300k/month to BDFL for removing two letters from an existing package's name? Deliriously happy, I think.

1 members found this post helpful.

By "full way apt-get" I understand the usage of the Debian's original apt-get, and this imply: Slackware replacing its package management with Debian's DPKG and APT-GET and adopting, of course, the .DEB packages with all dependency resolution which exists - including any extensions for remote repositories too.

So, you will still be deliriously happy OR you will run away yelling "Blasfemy!" IF our BDFL will justify this movement by increasing at least ten times his financial revenues, if not hundred times?

I for one, I will be really happy for him and I will continue to use a debianized Slackware as usual.

After all, I am truly habituated with Ubuntu's packages management - I use it since considerable longer time than Slackware, so will be absolutely no issue for me.

2 members found this post helpful.

Rather rpm based. rpm2tgz is still present while deb2tgz disappeared. I take this as I a sign of where is sympathy. For myself in future once stable will be released I will test script which supposedly allows to use Arch repositories. On non-Arch distributions. We'll see.

I have experienced rpm based systems, but not deb. So my preferred outcome would be simply running an eraser over part of slapt-get's name instead. But if BDFL decided otherwise, I'd live with it because I assume that pkgtools would still work, even though no longer "official" - just like slapt-get works even though it's not "official".

Deliriously happy, of course. And I would continue with debianised* Slackware (ignoring apt-get, just like with earlier distros I ignored the rpm equivalent (I've forgotten what it was called) and just like I ignore slapt-get now**)

*Alway assuming that the init which must not be mentioned doesn't make an appearance.

**Installed it, played with it and decided I had no compelling reason to use it.