Tim Bray on Nostr: 1/2 Looking at one of the #xz writeup, this struck my eye: “The release tarballs ...
1/2 Looking at one of the #xz writeup, this struck my eye: “The release tarballs upstream publishes don't have the same code that GitHub has. This is common in C projects so that downstream consumers don't need to remember how to run autotools and autoconf.” Ah, GNU AutoHell, I remember it well. Tl;dr: With AutoHell, even if you're building for a 19-bit Multics variant from 1988, it’s got your back. Except for it’s just too hard to understand and use, thus the above.
#infosec
Published at
2024-03-31 19:34:53Event JSON
{
"id": "41c662e093ef2274a77f0615cc5f09d4d33c62b7ce70433447561885337c77b8",
"pubkey": "973c779cb5e72ff0b6f0f47f8e86aee1face1c21b80ae0d9bc50968aa717e4b8",
"created_at": 1711906493,
"kind": 1,
"tags": [
[
"t",
"xz"
],
[
"t",
"infosec"
],
[
"proxy",
"https://cosocial.ca/users/timbray/statuses/112191503986825305",
"activitypub"
]
],
"content": "1/2 Looking at one of the #xz writeup, this struck my eye: “The release tarballs upstream publishes don't have the same code that GitHub has. This is common in C projects so that downstream consumers don't need to remember how to run autotools and autoconf.” Ah, GNU AutoHell, I remember it well. Tl;dr: With AutoHell, even if you're building for a 19-bit Multics variant from 1988, it’s got your back. Except for it’s just too hard to understand and use, thus the above.\n\n#infosec",
"sig": "c5161185b624f001c6ca91af71bbc14b65b54d5532d364a2b0affddda3f5427a4d7c668081b347d17a7fbc967e3c5af61dfa206d371169f0da6698bddd57f761"
}