<brian|lfs>
how many package managers does Slackware have these days?
<r0ni>
that's a rather complicated question
<r0ni>
already asked elsewhere
<r0ni>
;)
<brian|lfs>
lol
<r0ni>
islack ships with pkgtools, slackpkg and slackpkg+ (in extra on current) but there are tools for interfacing with SBo and other 3rd party tools for managing repos and such, it really depends on what you're after
<r0ni>
the problem with slack is it offers no way to verify any 3rd party stuff, so it's all a "do I trust this persons repo?"
<brian|lfs>
agree
<r0ni>
i only use current tho, and I just maintain all my own repos, therefor I am the only trust i need
ppetrov^ has joined #crux
<ppetrov^>
i see you guys discussed Slackware's package managers, I was surprised to read what r0ni said that slackpkg+ had been included in /extra. Good. I have been waiting for sbopkg to get there for many years
<ppetrov^>
no luck...
<r0ni>
yeah it's been taken over by alienbob for some time now, not sure how much (if any) works been done for it
<r0ni>
my personal opinion is sbopkg isn't worth the time investment and arbitrary ways it deals with deps, there's much better tools for sbo than that one
<ppetrov^>
r0ni, like sbotools? I liked sbopkg, because it "looked" and "felt" very native compared to slackware's pkgtools
<r0ni>
I tend to use 'sboui' as it has a nice mc-like interface and it can be configured some different ways, but its a nice client which does deps automatically, prepares the build order properly, can rebuild all deps or not and so much more
<r0ni>
'slpkg' is what all the kids use, and it does ok with packages and deps but i've only tested it on my own repos, and it manages deps and everything with only me including a 'slack-required' in my package much like slapt-get is designed but seems to fail at doing
<r0ni>
slpkg is unique in that it can do slackbuilds or packages all in one app, but it can't handle slackware+custom things well, it has to be one or the other
<r0ni>
i don't use sbo as it exists tho, so much poorly maintained software, I just keep my own repo for everything i use lol
lavaball has joined #crux
<ppetrov^>
slpkg was ridiculously slow in my experience
<ppetrov^>
but as always, it could be my problem...
<ppetrov^>
and in general, I grew to dislike, having separate tools for official packages management and everything else
<r0ni>
there has been a major re-write in the past few months, it's improved but its not perfect
<ppetrov^>
not as perfect as prt-get :P
<ppetrov^>
r0ni, at some point i had this sick enthusiasm to write a set of tools for Slackware to deal with SBo in a way mimicking the tools from CRUX
<r0ni>
and yeah my gripe with slack is all the tools i have to use, i try and stick to just slackpkg but i'm expanding my repos to be useable with other software and take advantage of it so i've had to learn some new stuff lol
<r0ni>
and well sbo is basically a ports collection, it's just implemented terribly
<ppetrov^>
im made an announcement at LQ, asking for help from experienced BASH coders, there was zero interest in the tools or getting help
<ppetrov^>
I agree about SBo, at some point I realized it was really dumb to have to change a package version in 3 places
<r0ni>
was that recently on the LQ post? I saw something metioning hoorex but i swear it was another user
<ppetrov^>
no
<ppetrov^>
what you was was sth else, with some really weird name
<ppetrov^>
I did the sboutils some 2 years ago
<ppetrov^>
my alsias at LQ is solarfields
<r0ni>
yeah, i think LQ is where i came across your blog, maybe you'd mentioned crux which got me here well before i even tried it out
<ppetrov^>
:)
<r0ni>
i spent two years thinking about installing crux lol
<ppetrov^>
and the you read my review of 3.7? :P
<ppetrov^>
the truth is, I would not be able to use CRUX if it wasn't for a ready kernel .config file (which I took from Slackware -current) and DE repos like your Xfce and jaeger's mate
<r0ni>
very likely , heh this was when 14.2 was getting a bit on and i was thinking, i need a future plan, having moved my email server off of slack cuz it got to be a pain maintaining all the packages that weren't included
<ppetrov^>
ah, I had a port in my blog about getting away from Slackware, because of the 14.2 -> 15.0 gap
<ppetrov^>
*port - post
<r0ni>
and now as 15 gets on, i've only kept my webserver on slack, cuz that don't matter to much in the grand scheme of things
<ppetrov^>
well, 15.0 is rather old already
<ppetrov^>
you said you use -current, what do you use instead of "revdep" there?
<ppetrov^>
i had asked this question at LQ and got replies like "we all have out home-made tools, maybe make your onw"
<r0ni>
heh a script i renamed 'revdep' heh
<ppetrov^>
Pat shared his script, whic does not work even nearly as good as revdep
<r0ni>
it's quite good enough for me, i can locate what package a lib belongs to easily since my repos are all legit so things can search the packages
<ppetrov^>
well, he's the author of Venom linux
<r0ni>
yeah, i've not tried that, but tbh it seems very close to crux in use and such
<ppetrov^>
yep
<r0ni>
i do love slack, but crux offers me the ability to cut out what I don't want safely, and with enough time one can do that in slack, but time... ahh life and time are our enemies
<ppetrov^>
heh
<ppetrov^>
i was a maintainer at SBo for over 10 years. I got used to making Pkgfiles very fast and I absolutely loved them
<ppetrov^>
otherwise, Slackware will always have a special place in hy heart
<ppetrov^>
awww, so romantic
<r0ni>
heh slack was my first actual install that lasted with linux, so it's always like home
<r0ni>
zipslack actually, if you remember that one
<ppetrov^>
the name kinda rings a bell, but i am not sure...
<r0ni>
was a 100mb slackware to fit on zip disk
<r0ni>
had basic system, you could add things to if enough space, that with fluxbox helped me learn linux better than any mandrake or redhat ever did
<ppetrov^>
well, fo course... when you are kinda _forced_ to learn :)
<r0ni>
20 year old me had nothing better to do, so it was the best tinkerers delight i could have come across, eventually i moved on to a full install, but that let me keep my trusty win98 while I learned heh
<ppetrov^>
heh...
<ppetrov^>
i started with linux when i was 22
<r0ni>
i just wanted to be able to run a website and have an ftp that didn't constantly freeze my OS, tho I guess using a laptop wasn't the best idea, looking back I sure learned a lot along the way
lavaball has quit [Remote host closed the connection]
brian|lfs has quit [Ping timeout: 260 seconds]
brian|lfs has joined #crux
brian|lfs has quit [Ping timeout: 248 seconds]
brian|lfs has joined #crux
lavaball has joined #crux
brian|lfs has quit [Ping timeout: 248 seconds]
brian|lfs has joined #crux
wreed has joined #crux
<wreed>
I just booted up the crux 3.8 ISO on my laptop, looks like I'm in a tough spot, you guys have the firmware for my wireless card, but not the module, and i'm having a hell of a time trying to build the rtw88 modules for 6.12.23 on my other machine to copy over
brian|lfs has quit [Ping timeout: 272 seconds]
brian|lfs has joined #crux
<jaeger>
Is that module part of the kernel tree or external?
<wreed>
It's part of main tree, its been backported by users before, but it's in the main tree. `drivers/net/wireless/realtek/rtw88` is the directory in the tree. I downloaded the source for 6.12.23 from kernel.org to check
<jaeger>
Looks like it's in the tree, I'll see if I can build it
<wreed>
I'd appreciate that. However if that doesn't work out, do you think I'd have luck with the unofficial iso? I'm downloading the latest to give that a shot
<jaeger>
Are you referring to the updated one? If so it uses the same kernel config and wouldn't currently have the module
<wreed>
Yeah, and alright, good to know.
<jaeger>
oddly selecting that driver in the kernel config doesn't seem to produce any module
<wreed>
really? the one specifically that my card uses is: wireless lan -> realtek devices -> Realtek 802.11ac wireless chips support -> Realtek 8821CE PCI wireless network adapter
<jaeger>
oh, there's a a submenu under rtw88, I see
wreed has quit [Remote host closed the connection]
wreed has joined #crux
<jaeger>
wreed: did that work?
wreed has quit [Remote host closed the connection]
wreed has joined #crux
<wreed>
No, sadly it didn't, but i appreciate your effort to help me regardless
wreed has left #crux [#crux]
wreed has joined #crux
<jaeger>
Was it missing some other module as a dep? Or something else?
<jaeger>
You can always install from the ISO without networking and recompile the kernel after if needed
<wreed>
the modules had "incompatible symbols", but i think ill probably just do the offline install and then rebuild
<jaeger>
Ah, wondered if that might be the case. I uploaded another set to the same URL as before, this time built directly from the ISO config
<jaeger>
Though I'm not sure if that would be enough to fix it
<jaeger>
In any case I can add the module to the ISO config and the next updated ISO build would pick it up
<wreed>
yeah, this is the first time i've ever had this happen; the rtw88 drivers are finnicky though, i have to permenently disable ASPM on the module or it turns into a brick after 30 seconds of not using internet lol. Like I said though I appreciate your help, thanks.
<jaeger>
weird, heh
<jaeger>
Sure, no problem
maledictium has quit [Ping timeout: 240 seconds]
dlcusa has joined #crux
maledictium has joined #crux
regenbogen has joined #crux
lavaball has quit [Remote host closed the connection]
lavaball has joined #crux
regenbogen has quit [Quit: Client closed]
wreed has quit [Ping timeout: 272 seconds]
wreed has joined #crux
<braewoods>
wreed, it can transform into a brick at will?! wow! sign me up!
<braewoods>
:D
wreed has quit [Remote host closed the connection]
wreed has joined #crux
wreed has quit [Ping timeout: 272 seconds]
brian|lfs has quit [Ping timeout: 252 seconds]
hsp has quit [Quit: WeeChat 4.7.0]
hsp has joined #crux
wreed has joined #crux
lavaball has quit [Quit: lavaball]
<wreed>
well i got booted with connection, i just enabled the modules when building the kernel
lavaball has joined #crux
<ppetrov^>
wreed, does it work on another distro?
<wreed>
The module? yeah, as i said earlier is a notoriously buggy driver but i can usually work around it by disabling aspm