• morto@piefed.social
    link
    fedilink
    English
    arrow-up
    1
    ·
    26 days ago

    I remember when games would’t work with wine, complaining about some dll, I would get it from some random shady site and drop into the wine system dir. Some of the times, it worked, to even my own surprise

    • terranoid@lemmy.cafe
      link
      fedilink
      English
      arrow-up
      1
      ·
      26 days ago

      “DLL finder”, holy shit I remember tools like that… God, now that I know how shared libraries work, that’s kinda terrifying people just saw that error message and downloaded whatever the fuck they found whereever they found it…

      Must be how some malware spread.

  • avocado@programming.dev
    link
    fedilink
    arrow-up
    0
    ·
    25 days ago

    Guys do not do this, it’s gonna cause a mess further down the line.

    “The problem with creating these links is that they aren’t managed in any meaningful way. If that library is removed, the link becomes broken. If the library is upgraded, it may encounter an error because of the link that it doesn’t expect to be there.”

    https://askubuntu.com/questions/461706/is-it-okay-or-not-to-symlink-libraries-to-overcome-cannot-open-shared-object

    • angband@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      24 days ago

      It is most commonly used to get an older archived program to load a newer library without recompiling the older program, so none of those objections apply, or are serious, because a dangling symlink (when the os moves to a newer library version) just keeps the one program from loading, reproducing (in a way) the error the symlink was introduced to fix.

      The user can typically fix the same exact problem in that case. Honestly, those objections read like that meme, “No, not that way!”

    • Skullgrid@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      23 days ago

      “The problem with creating these links is that they aren’t managed in any meaningful way. If that library is removed, the link becomes broken. If the library is upgraded, it may encounter an error because of the link that it doesn’t expect to be there.”

      If anyone is forwarding shit the way OP is, I’m pretty sure this is a “move the earth to hack this shit to work right now” action instead of “here are the foundations of my best practice based system”

  • Skullgrid@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    26 days ago

    What about setting up a new environment correctly instead?

    Says the man that just copied and pasted, then checked in 800mb of shitty angular dependencies just to get Jenkins to be able to build his inherited project.

    It’s ok, they don’t pay me enough to support a family and don’t give a shit about this project, and it’s for internal use.

  • x0x7@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    25 days ago

    Ubuntu problems. Just use Arch. Then all of your software is from the same era… aka current.

    • iocase@lemmy.zip
      link
      fedilink
      arrow-up
      0
      ·
      25 days ago

      I dont have this problem on Ubuntu somehow (yet?) Why does it happen to people?

      • Ŝan • 𐑖ƨɤ@piefed.zip
        link
        fedilink
        English
        arrow-up
        0
        arrow-down
        2
        ·
        25 days ago

        Lots of software isn’t “officially” available for Debian derivatives so þere’s more need for side-loading. You may not have encountered it because you haven’t yet come across some software you’d like to use which isn’t available in an official repos.

  • juipeltje@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    26 days ago

    Meanwhile as a guix+nix user i can just build it against that old library version because nothing can conflict with each other anyway