Instalación de Slackware 15 64-bits + Slackpkg + Slackbuilds + Sbopkg
@garpu oh I’m not talking about ##slackware but #slackbuilds irc. I wouldn’t even bother posting any kind of real question in ##slackware they don’t wanna hear a damn thing about it. 😆
https://slackdce.theworkpc.com/
THIS PROJECT, "SLACKDCE", OPPOSES THE USE OF #SLACKBUILDS. SLACKBUILDS RECOMPILE EACH SUBMITTED PROGRAM JUST FOR TESTING, THEN DISCARD THE RESULTING PACKAGE—WASTING A BUILD THAT COULD BE USED BY THE END USER. WE REBUILD THESE PACKAGES WITH CARE AND EFFORT SO THAT #SLACKWARE USERS CAN HAVE A PROPER REPOSITORY, JUST LIKE IN ANY OTHER LINUX DISTRIBUTION.
After weeks of little maintenance needed for my #SBo #slackbuilds, suddenly had four releases this week 😅:
- #dracut #dracut-ng 107
- #keychain 2.9.0 & 2.91.1, first releases in 7 years, #danielrobbins back
- #mbuffer 20250429
- #openzfs 2.3.2
Hey @vbatts I have upgraded few #SlackBuilds packages which you are the maintainer, #Podman and it's dependencies, I would like you could check it for later submit a MR to GitLab SlackBuilds.
https://gitlab.com/slackware-brazil/slackbuilds/-/merge_requests/111
I just pushed 7 updates for nwg-shell SlackBuilds to #SBo which I’d been putting off for weeks. Submitted typobuster yesterday and I need to push a few python upgrades yet. Trying to get it partially caught up (as best we can on 15.0). #slackware #SlackBuilds
@joel It's been a while since I've tested #pkgsrc on linux. I should compare my installed #sbo #slackbuilds to available packages in pkgsrc and give it a go
#PSA to anyone having issues connecting with #Slackware's main mirror and #Slackbuilds
@r1w1s1 @jbzfn @phoronix I submitted the update for #openzfs 2.2.4 to #slackbuilds.org yesterday. It should be available Friday or Saturday #SBo #slackware
@ParadeGrotesque I update my #slackbuilds for 9.0.0 but here I used only x86_64 :) but I plan to use more and more for my #openzfs tests.
I just migrate my #slackbuilds to @Codeberg and soon remove this project from #github
Hi all :) I create/update some #slackbuilds for #slackware-current
#HelixEditor
#procs
#alacritty
The repo have the link for the pre-build packages.
Let me know if you find any issue.
PS: I will try to compile some of then in Slackware15 but the main focus is the current/next-version.
There isn't #clojure #lsp on #Slackware community ( #slackbuilds ). Maybe I should submit one 👀
A member of #slackbuilds irc room keeps spreading false information that you can’t have webkitgtk 4.0/4.1 installed at the same time citing the soup2/3 libraries as reasoning. No matter how many times I tell him, you can, and every distro even ships them both installable at once he still keeps on. This kind of mis-led nonsense gets spread around the #slackware community and people believe this horseshit. 🙃
Yes source based distro's have been around since the very beginning - in fact, MCC Interim Linux and #SLS weren't far from that mark, except that they merely tried to make it a bit more convenient by packaging up tarballs to be exploded during installation. And there's always #LFS.
If you think about Slackpkg - and you consider that you can actually re-install the entire system by compiling every single component of the default (full) install with the evocation of a single command, followed by the customization of your entire system by installing every kind of software imaginable through the use of #sbopkg or some other automated, dependency resolving package manager that uses #SlackBuilds (which are downloaded, then exectuted, and subsequently download the latest release of he software package desired, which is in turn compiled, packaged, and exploded) - you actually have a fully source based distro installed on your box.
That's right - Slackware is (can be forced to be) an entirely source based distro installed on your device.
And choosing to convert from a point release to Slackware -current switches you from a point release to a #Rolling_Release distro.
*Debian Testing, aka at this time, Trixie is a rolling release. #Arch_Linux is a rolling release, SourceMage and Lunar Linux are source based distros based on #Sorcerer_Linux, the original fully source based Linux distro released when Linux was only about 8yrs old in 2000, and the #Gentoo or #Funtoo source based Linux distros.
SystemD my ass. That has nothing to do with nothing in that conversation - it's completely non-sequitur and truth be told, most source based distros (Arch, Gentoo) support the type of init system that *YOU CHOOSE. For Debiantards such as myself, well..... There's #Devuan - and that's very refreshing to actually have control over your system again with true init scripts. But I rarely use Devuan, even though I've been associated with the initiative since its inception, after leaving the #Mageia team several years ago.
As I state in almost all of my profiles, I'm a Slacker, since 1993 (Slackware Linux), and I'm also a bit of a #Debiantard. On the BSD side, after leaving #Jolix (386BSD) for Slackware, I've pretty much settled on either #OpenBSD or #Dragonfly_BSD, w/the awesome #HAMMER2 FS. I still have a lot of love for #FreeBSD and of course #NetBSD - where I spend a lot of time in my proper #Korn Shell....
But what the heck does any of this have to do with a comparison of using Gentoo Linux being akin to using SystemD?
I don't like SystemD - but if you're a realist, that doesn't mean you forgo using distros that only have that init tooling. You just roll with the punches and keep following the innovations that support you - NO ONE STILL RUNS WINDOWS XP in production - at least, no one outside of state mental hospitals, that's just insane to do in a forward facing business environment.
But a lot of companies do leverage OpenRC, SysVinit, etc., instead of SystemD - that's not going away, and SystemD itself and Poetering have their own up and coming challengers.
SystemD is (supposed to be, originally) a way to boot your box. Yes, it's indeed encroached upon other landscapes since, but not all of those constructs are even considered by many mainstream distros - it's not a fact of life. Other init systems thrive in the UNIX world to this day and will continue to do so.
Likewise, Source based Linux distros are just one among many distros that exist, and may or may not leverage SystemD as their init systems - to really get a good grasp of this, I recommend doing a few Arch Linux installs - with and without SystemD as the base init system. Heck, even Debian still supports your regular, good old #syslog, and at every turn during your updates, reminds you how to keep it enabled since the whole journalctl crap just isn't as elegant, IMO.
Personally, I think more concurrent options are usually better - space is cheap. Storage no longer costs a dollar a meg. or worse, like it was when I was a kid, a few thousand dollars a meg. That's right... MegaByte - Not TB for penny's!
Okay so now I'm waiting to hear back from the OP and see just what the heck they meant when I got triggered. In the meantime....
Enjoy installing and using #Sorcerer_Linux, or the subesquent forks of it's surviving lineage like #SourceMage and #Lunar_Linux - you're now a part of mainstream source-basedLinux History once you do 🤘 💀 🤘
#tallship #Linux #FOSS #distros #Sorcerer
⛵️
.
RE: https://social.sdf.org/users/tallship/statuses/111957857148746923
Update on my #SlackBuilds bulk builder progress: It's at the g's, and has been compiling gmsh for hours lmao
Soon, they shall all be built!
My #SlackBuilds bulk builder is alive! IT'S ALIVE!