• sonofearth@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    17 hours ago

    Fine agree with all of what you say. But still the AUR is the only repo where this happens majority of the times. So what to do next? I am sure the solutions I mentioned in a comment below are not that difficult to implement.

    • bitfucker@programming.dev
      link
      fedilink
      arrow-up
      1
      ·
      16 hours ago

      Sure, your proposed solution is a good way to weed out the low hanging fruit. But I don’t like that it may create friction for normal users. AUR was never meant to be a FOSS project on its own with a full time maintainer that maintains PKGBUILD and the infra.

      Like I said before, it is more akin to an internet forum and pastebin more than a full fledged package repository. And to be fair, it isn’t a package repo anyway. It’s like a cmake / makefile sharing site. Building and packaging for arch is just that easy compared to say, debian.

      If people want to use a repo, there is chaotic aur. Maybe that could be the way too. A dedicated community project to vet the AUR. Or the project maintainer itself could provide a pkgbuild directly on their repo.

      Just don’t ever blame the maintainer for providing a place to store something for free and open to anyone. Especially if it is your choice to get something from said place and be surprised that it is malware.