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": "2f419451e98c20e180a917cbf36773befe7f5592648677675c207f7b1fceb0b3",
"pubkey": "f7a38559b7ea4e7fdb539adbc6cd41f57281707885147c4f7f5ff4cdc2ff5f14",
"created_at": 1790105723,
"kind": 1,
"tags": [
[
"proxy",
"https://snac.bsd.cafe/r1w1s1/p/1790105723.125176",
"web"
],
[
"t",
"slackware"
],
[
"proxy",
"https://snac.bsd.cafe/r1w1s1/p/1790105723.125176",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://snac.bsd.cafe/r1w1s1/p/1790105723.125176",
"pink.momostr"
],
[
"-"
]
],
"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",
"sig": "76bb521e98a33b27ebad78e9ab3d7a1f1120b426dc4581e4882a5c12d1ee0600c013475c10192d3186119c099b1b44c09e04b48e2b4ef10836b9ae4c698a5d17"
}