Amitai Schleier
@schmonz@schmonz.com
Next problem induced by CLT 15.3.0.0.1.1708646388 damage, with probable fix: http://mail-index.netbsd.org/tech-pkg/2024/03/25/msg029053.html
Mac pkgsrc builds almost back to normal �
Today's: fix how #Xcode developer tools are found. http://mail-index.netbsd.org/pkgsrc-changes/2024/03/20/msg295628.html
Upcoming: avoid useless CLT install dialogs. http://mail-index.netbsd.org/tech-pkg/2024/03/20/msg029031.html
For #pkgsrc, no good. We build quarterly releases of >25k other-people's-code on dozens of platforms. What to do? https://mail-index.netbsd.org/tech-pkg/2024/03/11/msg028994.html
#pkgsrc has a "tools" abstraction to deal with this, so we've dealt with it: https://github.com/NetBSD/pkgsrc/commit/b889d0bc0d9edd0d04311ec0c36de73ed644ab4d
Individual packages may still pop up the CLT install dialog. Please report so we can fix them.
https://federate.me.uk/@jperkin/112059262183819297
When developering, I always want as much deterministic feedback as I can near-instantaneously get. I also want additional feedback that takes longer and/or is less deterministic, for which “CI” environments are considerably better than nothing.
You'll always know when you're visiting an editable page. And with the consistent Edit link at top right, you'll always know where to click.
https://schmonz.com/software/editthispage #WikiWikiWeb #wiki
nb
. N.B.: now boot, next build, new binaries, no biggie.It may be a different bug. The smaller reproducer in the bug report does not fail the first time I run it. I have to run ls trees/foo; touch trees/foo; ls trees/foo; rm trees/foo; ls trees
a second time to get into trouble.
https://github.com/NetBSD/src/commit/fee42fd1d9cec2db989eb928c110ccc4d911165a
With Greencently, it also has your back when you remember. Commit quickly and stay in flow.
https://github.com/schmonz/junit-greencently
#TDD #TBD #JUnit #Kotlin #Java
#JVM
https://octodon.social/@schmonz/111503108753559669
https://octodon.social/@schmonz/111503106299649849
https://octodon.social/@schmonz/111503106299649849
https://youtu.be/PNk9xjgJ3Zg?si=irFFBPgh3caHcVcP
https://octodon.social/@schmonz/111503105647057690
(Example of a pattern: when possible, I prefer to learn fewer things that compound better. https://schmonz.com/2013/06/10/area-under-the-curve/ says more. Thanks again, @garybernhardt.)
https://octodon.social/@schmonz/111503104723168218
I'm intentionally omitting some projects and forgetting many others. That's how it is after 2+ decades of contributing to Open Source. I'm not a big deal. I'm lucky. Besides itches to scratch, I've had big projects to bewitch me, and time and brain to invest in all of them.
Any wiki lovers remember the Universal Edit Button browser plugin? For any page advertising in-browser editing, it showed a consistent UI control. "Edit This Page" is a userscript facsimile: a bit less elegant, but far more broadly browser-compatible.
For teams whose commits fail if any tests are red, Greencently offers an optimization: your pre-commit hook can check whether you yourself just ran all the tests green "recently enough" (as defined by the team). Available for JUnit 5, so far. Would love more implementations.
pkgsrc is still managed in CVS, but my finger habits are gittish, so I recently came up with "cvs-for-gits", a small wrapper script that colorizes cvs diff
, adds cvs show
, and automatically pages long output from subcommands like annotate
, log
, and status
.
These solo creations led me to wish those of us modernizing qmail could team up. There was no precedent in the community for collaborative Open Source development (rather the opposite). But when I imagined notqmail aloud, some folks joined me. We're still at it & having fun.
qmail's packaging challenges led me to wish certain software existed. So I wrote it. rejectutils refactored conflicting patches as composable SMTP filters. acceptutils refactored TLS and AUTH for improved security. Happy accident of its better design: old tools do new tricks.
qmail (an insightful but rough-hewn MTA) has required sustained creative packaging effort. All of the package's very few users probably love it. Feedback from one: “Remarkable work in patching, modernizing and cleaning up qmail… well documented, and very straightforward.”
pkgsrc, a particularly flexible Unix package manager:
I led the initial porting to Mac OS X (when it was called that), continue to contribute macOS fixes, maintain over 150 packages, and have a couple dozen VMs with a variety of OSes and architectures to test and fix builds.
ikiwiki, a particularly flexible static site generator, one of the earliest in the genre, and still one of the most flexible:
I've contributed "fancy podcasts" (Agile in 3 Minutes uses it), rsync, CVS integration (the @netbsd and #pkgsrc wiki use it), and more.
🧵with some of my #OpenSource projects:
Hire me for what? An #EngineeringLeadership role. Details: https://schmonz.com/2023/08/05/who-needs-an-amitai #OpenToWork
Chat with me and others, see what I'm all about, today? Yes. Details:👇🏼
https://octodon.social/@schmonz/111488737018503494
12:15-12:45pm US/Eastern (2.5 hours from the time of this posting).
Very okay to:
- Be late
- Bring something to talk about
- Bring just your ears (must still be connected tho)
- Bring lunch
- Have stuff stuck between your teeth
https://us02web.zoom.us/j/85664294053?pwd=bGd2ODErbDVINSs3SGg1UUZRUm15dz09
Since we don't need to define very carefully or predict very much, we spend less time building no things.
https://octodon.social/@schmonz/111483227521521386
“Would you listen to ‘#Agile in However Long It Takes, Whenever’? I wouldn't feel as good about making it, that's for sure.”