Arch Linux User Repository

Alright, finally got an update pushed. Please let me know if anyone runs into any issues with it. For now at least I'm going to leave it pointing to the dev branch, since this is a VCS package and it seems that the merges to master are relatively infrequent.

@abcd567, I did see your combined repo. However, I personally would not adopt your method as it currently stands, as at a quick glance I see a number of issues. Your PKGBUILD, for example, does not separate depends and makedepends, and rather than utilize the build() function you are doing everything in the package() step. Additionally, your install script uses pacman -Sy to install dependencies, which is explicitly unsupported as this can result in partial upgrades.

@PanisSupraOmnia
Have you seen PKGBUILD at my Github repo "https://github.com/abcd567a/archlinux-piaware" ?
It builds a self-contained composite package, as it builds following 3 components enclosed inside the piaware package which it builds:

piaware
faup1090-fa
fa-mlat-client

I have used this technique of composite-packaging since Feb 2021
(https://discussions.flightaware.com/t/how-to-install-dump1090-fa-and-piaware-on-arch-linux-x64-86-and-on-alarmpi-armv7-aarch64/42366/14)

Subsequently using this compost-package technique, I created my above linked Github repository in May 2022.

Great, seen your Github repository and latest commit.

By the way, the mlat-client's dev branch was merged with master branch about a month ago, and both are now v0.2.13.

Good that you have added makedepends = python-wheel. I have forgotten to add it in my comments here.

If you like, you may look at my following repositories at Github:

https://github.com/abcd567a/archlinux-piaware

https://github.com/abcd567a/archlinux-dump1090-fa

https://github.com/abcd567a/piaware-ubuntu-debian-amd64

.

Yes, I'm aware. Point is that I don't currently have my piaware tracker set up, so I don't have a way to fully test it for a few days. The changes to the package step are already something I've handled, but hadn't pushed to AUR due to lack of testing. I mostly just needed to test that using python-build and python-installer works correctly.

For reference, here's the commit that I've pushed to GitHub: https://github.com/PanisSupraOmnia/pkgbuilds/commit/ce464b0653e2393a5f571c768da3dc3846724c61

@PanisSupraOmnia

Better you TEST the modified PKGBUILd by running "makepkg -si" and installing the finished package, to make sure all works OK BEFORE pushing the modifications to AUR. The reason is as follows:

In addition to changes mentioned in my previous post, I had to do following changes to "install -Dm755 -t ..." commands in package() {}:

DELETED Followin 2 lines:

install -Dm755 -t "${pkgdir}/usr/lib/piaware/helpers/" fa-mlat-client

install -Dm755 -t "${pkgdir}/usr/bin/" mlat-client

ADDED following line:

install -Dm755 ${pkgdir}/usr/bin/fa-mlat-client  ${pkgdir}/usr/lib/piaware/helpers/fa-mlat-client

.

@abcd567 Great, that's very similar to what I'd already done but still haven't had a chance to test. Since you've tested it I should be able to get an update pushed today.

Click on the link below to see the SCREENSHOT of Piaware logs, showing mlat is working on Arch Linux:

.

https://i.postimg.cc/44wKgpDK/Arch-Linux-piaware-with-fa-mlat-client.png

.

.

@PanisSupraOmnia

These are the modifications I have done to build mlat-client and fa-mlat-client on Arch Linux:

(1) Installed Python tools:

sudo pacman --needed -Sy python-build  python-installer python-setuptools python-pip

(2) In file PKGBUILD used master branch, no patch

CHANGED

source=("${pkgname%-git}::git+$url.git#branch=dev"
        "python-function-names.patch")
sha256sums=('SKIP'
            'c3645a1535418c1c0b083f101c07b8243c1ac947e21f07a501c868d95c3bf43c')
b2sums=('SKIP'
'123f866478b0100dce0efbca8db88a302ddc50aedf82153da6aa097874f6319908eceb1edb274f16edc8c6f09a51d56800d687c44aaf57dda2b6>

TO

source=("${pkgname%-git}::git+$url.git")
sha256sums=('SKIP')
b2sums=('SKIP')

(3) In file PKGBUILD in prepare(){}:

DELETED line

patch --forward --strip=1 --input="${srcdir}/python-function-names.patch"

(4) In file PKGBUILD in build(){}:

REPLACED:

./setup.py build

BY:

python -m build --wheel --no-isolation

(5) In file PKGBUILD in package() {}

REPLACED:

./setup.py install --prefix="${pkgdir}/usr

BY:

python -m installer --destdir="$pkgdir" dist/*.whl

Above build & install commands will make & save both the mlat-client and fa-mlat-client executable binaries as shown below.

NOTE: You will need to modify your "install -Dm755 -t " code lines to copy these to appropriate folders.

[abcd@archlinux-2023-11 ~]$ ls -l mlat-client-git/pkg/mlat-client-git/usr/bin/  
-rwxr-xr-x 1 abcd users 220 Nov 27 11:53 fa-mlat-client
-rwxr-xr-x 1 abcd users 213 Nov 27 11:53 mlat-client

.

That is all !! Enjoy :)

.

I have created a package which contains all the 3 following components in one piaware package:

(1) piaware (2) faup1090 (3) fa-mlat-client

I could successfully build fa-mlat-client v0.2.13 using source-code from master branch of mlat-client, by using different python tools to build & install, than those which were used previously. No patch required.

The patch that was previously necessary has been upstreamed, so it can be removed; however, there's been some other changes to it, so the existing PKGBUILD does not work. I think I have a good way to fix it, but I'd like to test it on my actual receiver in the next couple of days to be sure I'm pushing something that actually works.