63
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 22 Oct 2025
63 points (100.0% liked)
Linux
10001 readers
334 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 2 years ago
MODERATORS
The middle ground, IMO, is not letting it spit out code.
Its almost certainly terrible, every time. Sometimes though... Its just mostly bad.
Ive found it useful for finding errors and potential optimizations though. Just not, you know, letting it actually write anything.
But letting it review and seeing:
Thats useful! Helpful, even.
Just not the nonsense it makes on its own.
Are SPEC files for RPM creation code? How much actual code is even written under the Fedora umbrella, except maintenance scripts and such? Adjacent projects such as Anaconda are in the rhinstaller organization on Github: https://github.com/rhinstaller/anaconda
Either I overlooked the details or they aren't spelled out. From my experience of packaging software for myself as RPM (for openSUSE) the amount of actual code are a few lines of bash scripting to invoke sed and such.