• 0 Posts
  • 16 Comments
Joined 2 years ago
cake
Cake day: August 5th, 2023

help-circle
rss

  • I think you have the wrong mental model of how the AUR works. You don’t enable it and then it works with pacman (which is what it sounds like you are thinking). Instead, it’s a repository of packages that require a different method of installation. This is described in section 2 of the wiki page you linked:

    1. Acquire the build files, including the PKGBUILD and possibly other required files, like systemd units and patches (often not the actual code).
    2. Verify that the PKGBUILD and accompanying files are not malicious or untrustworthy.
    3. Run makepkg in the directory where the files are saved. This will download the code, compile it, and package it.
    4. Run pacman -U package_file to install the package onto your system.

    More detailed instructions are on that page.

    However, if you want a pacman-like experience, you can install an AUR helper. You’ll still need to install the AUR helper via the steps above, though.


  • Email isn’t “the only way” to send patches. In fact, he addresses that:

    It doesn’t have to be by email, either. Any method of sending this data to the maintainer is fine. For example, I’m on Mastodon – so you could send me a repository URL via Mastodon if you really wanted to (provided you didn’t mind my responses being very short). Or you could send patches via any other communications medium that you and the maintainer are both on, if it lets you attach files to messages.

    His preferred method is just sending a URL over email. You can use any communication method if you both already have an account.


  • If it’s on Github doesn’t that make it OS?

    No, when talking about open source software, people typically refer to a definition along the lines of the Open Source Initiative’s Open Source Definition. To distinguish this from software that you can only see the source (but don’t have rights to copy and modify it), they’ll use the term Source Available Software.

    I don’t really know about the software you guys were talking about, but the repositories I looked at used the MIT license, which is OSI approved. However, that might not be all of the code they use. It’s not uncommon for a company to open source a “base” version, but they deploy a version that’s altered from that (I’ve got no clue whether they do or don’t).









  • Now my question is, how should I deal with these pacnew files? should I always remove them, always replace them, always read them and decide?

    Always read them and decide what to do. However, what to do usually isn’t too remove or replace them, but to update them with the changes instead. Most text editors have a way of looking at a diff of two files. This will highlight the differences and you can decide based on the individual changes (maybe it’s something you purposefully changed, maybe it’s a change to the default). If you use vim, vimdiff will do this.

    I’d rather not read these things everyday, it’s a bit boring, so I hope there’s a better solution. How do you deal with these?

    After you make your decisions on what to do, delete the pacnew, otherwise you’ll keep getting messages about it. They don’t get updated all that often (except mirrorlist, I usually just delete that and run reflector every once in a while).