[Slackbuilds-users] incrementing?

David Chmelik davidnchmelik at gmail.com
Thu Jul 31 00:32:54 UTC 2025


On 7/28/25 5:10 PM, Willy Sudiarto Raharjo wrote:
>> Many SlackBuilds work incremented but haven't been updated or are 
>> abandoned (though I can't takeover more because of increasing home/ 
>> family responsibilities while trying to work more hours).  Two of 
>> these are element-desktop (years behind) and palemoon-bin (months 
>> behind) and I don't know about palemoon (making/compiling) but that 
>> at least used to work (even more years behind).  Slack (unfortunately 
>> named chat program) would be able to increment (possibly this Spring) 
>> if it used .rpm, but unfortunately maintainer uses a horrible Ubuntu 
>> 'snap' one can't even find latest ones to download to tr increment.  
>> I hate when .snaps, flatpaks are used over .deb, .rpm and when these 
>> are used over tarballs (which can be binary) unless it's meant to 
>> be--and labelled as--binary (package-bin).  Can team reach out to any 
>> such or other maintainers asking if they'll update or could just be 
>> incremented, and can any of this be automated if okay/worthwhile to 
>> do?  When I 'sbocheck' recent years I have more & more dozens needing 
>> updating. Many are updated by alienBOB, slackers.it, or others before 
>> getting to SBo months/years later, but I don't know which or how many 
>> yet... I just wish some this was also listed so users can increment 
>> on their own at their own risk even to help test and report if 
>> something may need improvement in SlackBuild (maybe finding more 
>> optional dependencies).
> Feel free to contact the maintainer if you need them
Since I've 1,600+ SlackBuilds but mostly don't find out, that 's mostly 
very unlikely unless there can be a list what's old/outdated (maybe soon 
there's a way you could automate checking for new source code?) in which 
case I'll try to do my part for interesting/useful ones.  I installed 
maybe 10 times more than I use (so 90% I simply won't find maybe until 
they're years behind/broken) which I plan to try/learn and am very 
slowly doing so, though interesting ones are regularly added.
> if you don't get response within 1-2 weeks, feel free to take over or 
> send updates
For ones I mentioned--and why (which is slowing down even my own 
SlackBuilds)--again, no.  For others /if I can find out by there being a 
list/ I'll consider.
         'Slack' is the .snap--almost 1.5 years old (five versions 
behind)--with no way to find any newer; only .rpms, which rpm2txz 
works... official 'Slack' is only my last option for when libpurple 
(BitlBee, Pidgin), Ferdium, slack.com web-chat don't work so unlikely 
I'll ever need official Slack again... but for those who prefer (easier 
than some alternatives) they might want latest or to know what happened.



More information about the SlackBuilds-users mailing list