Arch Linux

dafero

Member

From: /home/dafero

Registered: 2014-03-22

Posts: 30

AUR: package with different names as dependency

Hello,

I'm adding my first package to the Arch User Repository.
It's a python2 program and it should install fine on all the architectures.

The thing is, this package depends on another package that changes its name depending on the system (the version for the RaspberryPi adds *-rpi to the package name)

I want my package to be available for all the architectures. How can I solve this issue?

Thanks!
Daniel,

---

sudo yaourt -Syua

WorMzy

Forum Moderator

From: Scotland

Registered: 2010-06-16

Posts: 11,869

Website

Re: AUR: package with different names as dependency

What package is that? There should be no need to change the name of a package based on the architecture it is installed on. If there was an overwhelming reason to change the name, I would expect the new package to "provide" (see 'man PKGBUILD') the regular package. That's an Arch ARM decision though, nothing to do with Arch Linux.

If the ARM package doesn't "provide" the regular package, then the only thing you can do is add a comment to the PKGBUILD explaining what an ARM user would need to modify for the package to build on their system.

---

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

dafero

Member

From: /home/dafero

Registered: 2014-03-22

Posts: 30

Re: AUR: package with different names as dependency

The conflicting package is libcec.
On the RaspberryPi the name of this package is libcec-rpi however on my desktop is just libcec.

Thanks!

---

sudo yaourt -Syua

atomicbeef

Member

Registered: 2015-09-30

Posts: 98

Re: AUR: package with different names as dependency

The PKGBUILD for libcec-rpi on Archlinux ARM provides libcec, so you should be able to just depend on libcec without any issues. The PKGBUILD for libcec doesn't change its name depending on the architecture (libcec-rpi is a separate package).