C-a k y
| pgp | 01EF9314E5638E1E44FCEF559CBD4CF409E7C52B |
jwatt
- 39 Followers
- 101 Following
- 1.1K Posts
Cajun Commie. Nerd. Swamp socialist. Engineer. Programmer. Dad. Linux, BSD and all open systems stuff enthusiast. Music fan.
Will the firmware be upgraded, by and by Lord, by and by. There's a better version waiting, in the sky Lord in the sky.
Listen to track in TIDAL - J A Y E L E C T R O N I C A: A.P.I.D.T.A.
I should re-read the Nix paper again. I’m sure it covers some of this. But, seems like you could have “files” that are links to instructions for building from which you can link to built artifacts, as long as they match. Then make some choices over when to use “cached” ones v. built ones. Yeah, I guess guix and nix do a lot of this. I need to explore them more.
fundamentals of build: You want one of 3 things:
1. artifact (binary) for your target or
2. Perfect runnable instructions for building artifact (bin) for your target or
3. Runnable instructions for building artifact on a variety of targets that you have tested on your target.
This allows for `1 || 2 || 3`. Good #buildtools take this into account. #Nix, #bazel, even good ol' #GNUMake. But, then we don't use that functionality; we forget about it in our scripts & they fail, missing a bin they coulda built or they fail, building a bin they coulda stolen. Note that this post puts off worrying about dependencies, because 1, 2 & 3 can worry about those, too, if you do it right.
movie pitch: it's Cyrano de Bergerac or Roxanne but I'm steve martin and the love letters are to Unix and they're idiomatic sh or bash scripts and I write them for programmers because they suck at writing them but then I fall in love with Unix and I just want the other programmers gone now
Even if you don't use them directly in your work or projects, it's good to look at and try to understand good software and tools like `bazel`, and I think even if you don't use it, looking at the BUILD files, etc can help you. For example, having toolchain setup, like bazel does, is smart as heck. Like, you can do that in a Makefile, too, ya know? And, I was just reminded of, e.g., these rules_docker and how the build rules are constructed in such a way that you can compose things so that other rules use containers or rules run in containers. That's a great way to organize those, too. Concepts. They're all over the place. https://github.com/bazelbuild/rules_docker#setup
I’m so cool as soon as I do anything it’s immediately a cold case