Skip to main content

in reply to daniel:// stenberg://

I see we are of the same school of cable management. I too use the same if-i-dont-trip-on-them-its-good-enough tactic.
in reply to Gabriel Adrian Samfira

@gabriel hehe, that photo is actually a little old. I eventually caved in and I have a slightly more organized cable situation now... but only slightly
Unknown parent

daniel:// stenberg://
@gbraad the left one of the drawings - of me (!) in a curl shirt -is from my daughter from maybe 10 years ago, the second (the curl laptop) is a newer one from @kushal's daughter. They're just great.
in reply to daniel:// stenberg://

quick question: in section “With Docker” there is a line

$ git co curl-8_8_0

Am I correct in thinking that “co” is a local alias that you set for “checkout”? If yes, this might confuse people when they try the code.

in reply to daniel:// stenberg://

It's not, if the xz incident hadn't happened, I wouldn't have known about the many projects focused on reproducible build and supply chain security, but it's great to see them now, few of them are:
github.com/kpcyrd/rebuilderd
openssf.org/blog/2024/01/18/in…
tlog.linderud.dev/
github.com/mozilla/supply-chai…
github.com/google/rust-crate-a…
This entry was edited (6 months ago)
in reply to daniel:// stenberg://

Would it make sense to use the timestamp of the git tag as the default value for SOURCE_DATE_EPOCH? Or have an option for the build script that does that? I think (some?) Debian packages use the timestamp of the latest debian/changelog entry like that.
in reply to ilmari

@ilmari that's a pretty clever idea indeed. I think I'll try to switch over to that for my scripts...