• frozenspinach@lemmy.ml
    link
    fedilink
    English
    arrow-up
    3
    ·
    5 hours ago

    one of my least favorite things about arch and other rolling distros is that yay/pacman will try and recompile shit like electron/chromium from source every few days unless you give it very specific instructions not to

    My understanding is that constantly triggering compiling like that shouldn’t be happening in any typical arch + pacman situation. But it can happen in AUR. If it does, I think it’s a special case where you should be squinting and figuring out what’s going on and stopping the behavior; it’s by no means philosophically endorsed as the usual case scenario for packages on arch.

    There’s certainly stuff about Arch that’s Different™ but nothing about the package manager process is especially different from, say, apt-get or rpm in most cases.

    • jwmgregory@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      1
      ·
      4 hours ago

      saying it can happen in the AUR feels disingenuous to me when you consider how integrated the AUR is to the arch ecosystem. this is a genuine complaint from a user perspective and is an issue with the design philosophy imo. it is a special case but it’s so frequent as to be annoying, is my point.

      not sure why everyone is replying like i’m unaware and totally ignoring the actual grievance i have. im very well aware of pacman and yay’s intended behaviors, i just think they’re shit in some cases. idk if people who say this have never tried to daily drive arch before or something but the AUR is absolutely not optional unless you want to constantly hand roll your own shit. see my edit to the original comment.