r1w1s1 on Nostr: Slackware-current is not simply a repository where every new upstream release gets ...
Published at
2026-09-22 19:35:23 UTCEvent JSON
{
"id": "3d70b1afc2ea9792c31790b1cb882d0d25a7606d5505f7cc2320b0cd345a3000",
"pubkey": "bd4d86a4807a90378a0fa1f20275e559cec20a24001ab3b1c97b2025706aad45",
"created_at": 1790105723,
"kind": 1,
"tags": [
[
"t",
"slackware"
],
[
"proxy",
"https://snac.bsd.cafe/r1w1s1/p/1790105723.125176",
"activitypub"
],
[
"client",
"Mostr",
"31990:6be38f8c63df7dbf84db7ec4a6e6fbbd8d19dca3b980efad18585c46f04b26f9:mostr",
"wss://relay.ditto.pub"
]
],
"content": "Slackware-current is not simply a repository where every new upstream release gets pushed automatically.\n\nThere is curation and integration before changes land, with Patrick Volkerding playing a central role in that process.\n\nI run -current on 3 physical machines + a VirtualBox VM I use professionally every day. It has been remarkably reliable.\n\nInteresting discussion on Reddit:\nhttps://www.reddit.com/r/linux/comments/1w96px4/slackware_16_alpha_1_available_following_gcc_162/\n\n#slackware\n",
"sig": "9971383f5edf70c6cb99886dbb25d5562b2cc432f077d12a9ea26c800aff831a3ca360ccf457112512558472550e3304919a894e2e8019cb7877bcb183ba7a06"
}