Arch Linux User Repository

To all having an issue with this driver: please try https://aur.archlinux.org/packages/rtl8814au-aircrack-dkms-git alternatively.

@erkexzcx: I have added you as co-maintainer. Thanks!

@erkexzcx: this is a bit unfair, in my 2018-07-16 message below I explained I was interested in merging your changes into my PKGBUILD. I just explained that the code needs to be put on a Github acount to be able to use it in the source() section. I have not heard from you since then, and assumed that like me and many others you might be on holiday. I am also between two countries at the moment, hence the lack of repsonsiveness. But please be reassured that all good will is very much appreciated. Are you still happy to merge with my PKGBUIlD then? I can add you as co-maintainer if this is agreable to you.

@erkexzcx this is not the case: everyone wants to help you (and others) and good as possible.

Feel free to create your own package, and if possible create a PR to the main repo.

I've put enough effort trying to make this package available for all devices supported in AUR, but nobody else seem to care. I will create another AUR package for this driver.

@francoism90: thanks I will look into it. I was under the impression that the multiarchitecture support in PKGBUILD was here to avoid multiple packages, but I understand the overhead here.

This needs an upstream patch to enable ARM support. I don't know if setting the ARCH to ARM is correctly, if I'm not mistaken another bool needs to be set in the Makefile.

My solution would be to fork the repo, do the changes and create a new package with -arm if no one can test/verify the changes.

@erkexzcx: I think the best way would be for you to create a Github account and put the file structure of your zip archive in a project. Then we can start diff between your archive and gordboy's one, to see what changes were required for ARM. Then we can see how we can incorporate these changes as a branch in my copy of gordboy's code. I am not familiar with the handling PKGBUILD for several platforms, but I will look into it. Either the platform detection will be made directly in the source (a bit like for the various linux kernel version), or maybe we can make the PKGBUILD download the specific branch according to the platform. I need to read how this is usually done. Thanks anyway for your contribution and I am glad this is on good tracks.

@zebulon I am not very familiar with makefile structure, but my proposed package https://drive.google.com/open?id=1rKsYlV7_8UUDLDsQzk6kxKtb0jbPXulu works just perfectly on 2 of my arm devices. Any suggestions of how this could be implemented? Instructions are here: https://edimax.freshdesk.com/support/solutions/articles/14000063861-how-to-install-ew-7833uac-adapter-on-raspberry-pi (this is exactly what my proposed package does for ARM architecture)

@francoism90: this is ok and I accept this argument. However we need to have a way to follow the code changes from the vendor's base code. Since my code is in Github, I would suggest to add arm as a patch set.

@zebulon It doesn't matter what architect your package supports. Not saying you can do anything in AUR, but other platforms such as ARM and x86 are fine to include if supported by upstream.