[Slackbuilds-users] start SlackBuilds-current-users / news:gmane.linux.slackware.slackbuilds.current.user ?

dchmelik at gmail.com dchmelik at gmail.com
Mon Dec 11 05:07:48 UTC 2023


If SlackBuilds.org (SBo) staff not only don't 'support' 
Slackware-current (I forgot) (some SBo maintainers including myself 
support Slackware-current) but don't want people discussing 
Slackware-current, then  shouldn't there be SlackBuilds-current-users / 
news:gmane.linux.slackware.slackbuilds.current.user?
     I tried to make habit of writing '[Slackware-current]' in subject 
lines.  After over five years from Slackware 14.2 to 15, many/most 
people I know who do much with Slackware used Slackware-current several 
years, and so did I, which seemed stable enough 99+% the time, so I 
never switched back to Slackware-stable except spare PCs and chroots 
(SlackBuilding/testing, fallback). Slackware-current seems so stable 
that for years I often forgot I'm using it (more stable than 
Devuan/Debian/Ubuntu/Mint/KDE_Neon 'stable' versions I administer for 
users).
     Things I post here recent years normally aren't problems/questions 
rather than what I repeatedly see from queues stopping early in sbopkg & 
sbotools, and wondering if anyone else saw (usually not stuff I use 
much/anytime yet, just testing). I didn't mean to waste anyone's time.  
However, I don't want to have to use a web-forum rather than 
listserv/mailing-list/NNTP/Gmane.

Sincerely,
David Chmelik (abridged Melik)
mirror.davidchmelik.com / mirror.davidchmelik.com/math/slackbuilds (most 
uptime)
davidchmelik.com / slackbuilds.davidchmelik.com (updates first)



More information about the SlackBuilds-users mailing list