When using software and the codecs from the packman repo, what are the best practices associated with the updating and maintaince of these packages and the system in general. Do I have to wait for sometime before updating using dup or can I use the packman modules of mesa with updated versions of the mesa modules provided officially¿? Are their dependcy issues for software sourced from packman.

  • ch8zer@lemmy.ca
    link
    fedilink
    arrow-up
    3
    ·
    edit-2
    1 year ago

    I’ve found it best to avoid the pacman repo. It can leave my system in such a weird inbetween state. Seeing as you mostly want codecs I tend to prefer flatpaks for VLC, Firefox, etc.

    If you insist on pacman, just wait. If you try to dup and have a conflict it means that either pacman or suse repos aren’t all updated so hold on a few days and you should be able to dup with no issues.

    • Sentau@lemmy.oneOP
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Do you also use the mesa pacakge from packman repos. Will zypper automatically use the packman package of mesa when updating if you do the vendor change for mesa from official repos to packman. I am asking because when I tried TW, different versions of packages in mesa were somehow simultaneously installed after a dist-upgrade and mesa was broken

      • not_amm@beehaw.org
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        Yes, I also use MESA, but that only happens when you use the --allow-vendor-change option. I don’t, I prefer to wait until packman is in sync with the openSUSE repos. I had that problem previously, before reinstalling TW and I didn’t like having multiple packages out of sync and sometimes repeated, I like to see them as a bigger package that has to be updated at the same time.

        • Sentau@lemmy.oneOP
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          So how did you replace the mesa version. Every documentation I see seems to tell of the --allow-vendor-change option