community and extra repo, what to do?

[crazycusti]

Hey!

i missing many of the community and extra packages for my new shiny arch-xserve g5! so what can i do? a guide or packaging rules would be nice 👍

or can i serve a buildbot? i have many g4/g5 cpu-native resources.

greets!

[kth5]

I am using pakku etc on x86_64 when I have no choice to use my own box, more often than you'd think...

Anyway, on powerpc that is a tad different since nothing exists with powerpc in mind. Meaning, one can't use tools like pakku to automate package compilation and installation.

Now, there are currently two options:

• AUR/community/extra etc Download the PKGBUILD folder as snapshot, add arch=(powerpc64le powerpc) and try to build.

• Modify pakku Pakku can essentially work on any architecture that nim supports, so it could be mended to ignore the fact AUR packages don't usually have arch=() set correctly.

I haven't gone with step two or add documentation due to limited about of time. The latter making me focus on more immediate things.

Wouldn't mind to do it over the coming holidays though.

[XieJiSS]

EDIT: Oh heck, I didn't realize that arch-xserve g5 is PPC. Just ignore this :-) Or maybe you can try your luck as patches for riscv64 might also fixes errors for PPC. Must apply them manually and makepkg -si yourself, though.

Hi @crazycusti, at PLCT Lab we are also working on the packaging & porting process of Arch Linux official repo (core, extra, community). You can get more details from https://archriscv.felixc.at/

You can add our repos to your pacman.conf, and install the keyrings.

[core]
Server = https://archriscv.felixc.at/repo/$repo

[extra]
Server = https://archriscv.felixc.at/repo/$repo

[community]
Server = https://archriscv.felixc.at/repo/$repo

[unsupported]
Server = https://archriscv.felixc.at/repo/$repo

If you use both projects' repo simultaneously, probably there would be conflicts. To avoid that, you can restore your pacman config, and compile packages manually. First of all, clone this repo, asp checkout the package and cd into trunk/, and then apply riscv64.patch grabbed from the previously cloned repo with patch -Np0 . After that, copy all other patches to the trunk/ directory (which should be the current working directory), and run makepkg -si. More information can be found in the Wiki (including some English ones).

[kth5]

I wouldn't recommend to mix repo use from Arch POWER with other distributions or vice versa for mentioned reasons indeed. Archriscv is quite the different cup of tea, especially the focus on a sole ISA, more often than not that will break powerpc* I imagine.

best is to use upstream AUR still and make employ -A if you need to build something on either end.

[kth5]

Also, I find distributing just patches fairly cumbersome. It can't be hosted standalone - not that Archlinux will go away any time soon, I hope - besides, we do have git. So I see no reason to. I'm a full PKGBUILD or die kinda guy. :P

[kth5]

Closing this for inactivity & it's only a historically relevant ticket.