• 7heo@lemmy.mlOP
      link
      fedilink
      English
      arrow-up
      10
      ·
      edit-2
      3 months ago

      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…

      • Bogasse@lemmy.ml
        link
        fedilink
        English
        arrow-up
        4
        ·
        3 months ago

        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.

      • flying_sheep@lemmy.ml
        link
        fedilink
        English
        arrow-up
        1
        ·
        3 months ago

        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

        • Corngood@lemmy.ml
          link
          fedilink
          English
          arrow-up
          8
          ·
          3 months ago

          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.

          • addie@feddit.uk
            link
            fedilink
            English
            arrow-up
            5
            ·
            3 months ago

            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.

            • Corngood@lemmy.ml
              link
              fedilink
              English
              arrow-up
              2
              ·
              3 months ago

              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.

              • flying_sheep@lemmy.ml
                link
                fedilink
                English
                arrow-up
                2
                ·
                3 months ago

                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.

            • Hello Hotel@lemmy.world
              cake
              link
              fedilink
              English
              arrow-up
              1
              ·
              3 months ago

              Its a good practice to make the auto generated code a part of the .gitignore list. Any language installable on peoples machines can be used to build these makefiles. Ya know a language is on that list? Makefile!

  • dhork@lemmy.world
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    1
    ·
    3 months ago

    Hey Torquemada, whaddya say?

    I just got back from the auto-de-fe

    Auto-de-fe? What’s an auto-de-fe?

    It’s what you oughtn’t to do but you do anyway…