• macniel@feddit.org
    link
    fedilink
    arrow-up
    5
    arrow-down
    1
    ·
    2 days ago

    The location of a binary executable matters less now than ever, and it’s location on the filesystem doesn’t matter whatsoever. It’s up to whomever packages and nothing more. As long as it’s documented, it doesn’t matter.

    But what if another program expects said user-level-system-binary in that very location?

    • just_another_person@lemmy.world
      link
      fedilink
      arrow-up
      3
      arrow-down
      5
      ·
      2 days ago

      Then you package them differently to address the naming. It’s not rocket science.

      If there are two people named “Tom” in a room, do you just give up and walk out of said room because it’s impossible to find a way to communicate in a room with two people of a similar name? No.

      • macniel@feddit.org
        link
        fedilink
        arrow-up
        3
        arrow-down
        2
        ·
        edit-2
        2 days ago

        No, but its like you expect your Milk to be in the fridge but its not there, but instead someone put it in the fridge of your neighbour for whatever reason. Why would you look there?

        • just_another_person@lemmy.world
          link
          fedilink
          arrow-up
          2
          arrow-down
          10
          ·
          2 days ago

          Ever dealt with packaging files? You tell them where to go. It’s a simple manifest that says where files get unzipped and put on the filesystem.

          You have zero idea WTF you’re talking about.

          • johannes@lemmy.jhjacobs.nl
            link
            fedilink
            arrow-up
            4
            arrow-down
            1
            ·
            edit-2
            2 days ago

            And how does this work when you expect a binary of someone else’s package in a certain location?

            Are you trolling or what?

          • macniel@feddit.org
            link
            fedilink
            arrow-up
            3
            arrow-down
            1
            ·
            edit-2
            2 days ago

            No I haven’t dealt with packaging files. But packaging files implies that you know where your files are.

            But as I stated it’s not about your own files but files from someone else you rely on.

            Imagine what havok you would cause when someone things it would be a great idea to put ls or login no longer in /bin but /sbin instead?