82
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 07 Apr 2024
82 points (93.6% liked)
Technology
59298 readers
1847 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
Honestly, if the makefile is well written, I will take that any day. Good makefiles are 😙👌.
They are extremely rare, tho...
I guess the solution would be a declarative language that compiles to makefiles. So that people don't have to know the nitty gritty of writing good makefiles, and can just maintain a file of their dependencies and settings...
I've always conjectured that good Makefiles existed but never seen one (or only for tiny projects). The core semantic of Makefiles is clear and straight to the point, I think the issue is in all the magic that was added to that to spare a few lines.
Perl? I had fun compiling perl from source back in the day.
IMHO the issue is two folds:
Why compile to a Makefile? You'd end up with automake gunk all over again. Just use cmake or so, where the declarative language replaces the Makefile entirely
cmake compiles to makefiles as well (it just also supports some other backends). I'm not sure why that matters though. In both cases the makefile is generated.
Not that I'm the biggest fan of CMake's syntax, but they are fairly concise and standardised. The XZ backdoor hid in amongst thousands of lines of autotools jank that very few people would be able to audit. A short CMakeList that generates a Makefile is a much harder place to hide something nefarious.
There's actually not that much autotools jank, really. There's configure.ac and a few Makefile.am. The CMakeLists.txt in the root is bigger than any of those files.
There's also some stuff from autotools archive in m4/. IMO that's a bad practice and we should instead be referencing them as a build dependencies.
I'm not convinced this backdoor would have been significantly more difficult to hide in the cmake code.
My point was that packagers should use straight up VCS and run all build tools instead of relying on partially pre-built tarballs uploaded by the upstream maintainers.
Oh yeah, that was pretty much the point I was trying to make too.
Its a good practice to make the auto generated code a part of the
.gitignorelist. Any language installable on peoples machines can be used to build these makefiles. Ya know a language is on that list? Makefile!It does? I guess I never looked inside that build directory.