• 0 Posts
  • 284 Comments
Joined 3 years ago
cake
Cake day: June 12th, 2023

help-circle



  • That doesn’t follow. What I think you mean is that by defining the constraints so rigorously, you’ve basically solved the problem yourself. But that’s exactly the point. The LLM isn’t the problem solver, it’s the execution engine that does the wiring-up and the ticking of boxes. The easy part, arguably, sure. But still considerable effort that can be saved, and that effort may be better spent on the problem-solving + constraint-defining stage.

    Mandatory disclaimer that this is not a pro-AI post. I also don’t agree that this setup works, anyway. It’s a classic Bob Martinism, the idea that writing good enough specifications makes the implementation irrelevant; it’s the type of idea that is allergic to reality








  • Using aur helpers is fine if they make it easy to read the pkgbuild, which paru does. It’s too annoying to check for PKGBUILD and upstream/vcs updates for each package individually.

    Ideally the aur helper would point out when 1) a package changed maintainers since your last install, 2) a package’s PKGBUILD itself changed (not just the upstream/vcs source), 3) the PKGBUILD is less than 24h old or so. And for #2, it should also show you the changes similar to what you see on the AUR site’s “view changes” page. I’m not aware of any aur helper that does these things, but hopefully recent events prompt a change.