Arch Linux User Repository

@solstice, this idea makes sense. I updated the upstream sample file to point to /var/cache/pacoloco. Or to be exact I commented this config option out and let pacoloco use the default location (/var/cache/pacoloco). Please check it and let me know how it works for you.

Could you use /var/cache/pacoloco as cache_dir in the /etc/pacoloco.yaml file, please ?

And create that directory in the package too ?

Because /tmp is for transient file, lost after a reboot. Moreover, /tmp is a tmpfs in RAM on archlinux, by default. This is hurting /tmp space available for other apps ,and limit RAM, unless this is swapped to disk.

As you are the dev, may be you can backport that to upstream in pacoloco.yaml.sample, may be ?

@wallace11 okay let's add armv7h to the list of supported arches.

@anatolik I usually ignore arch when building on ARM, yeah. However, I don't know of any AUR guideline preventing package maintainers from adding ARM to the list of supported architectures, even though Arch does not officially support it, so I guess it shouldn't do any harm to include it if it works...

@artodeto pacoloco itself does not know anything about difference between arches. Pacman just proxies downloads for a given URL.

If you need to proxy pacman databases for different arches then you need to have multiple different repos:

repos:
  archlinux_x86_64:
    urls:
      - http://mirror.lty.me/archlinux
      - http://mirrors.kernel.org/archlinux
 archlinux_arm:
    urls:
      - http://foo.bar/archlinux/arm
      - http://bar.foo/another_arch_arm_repo

Then modify pacman.conf to point to the repo with the required architecture http://myserver:9129/repo/archlinux_$arch

@wallace11 just curious aren't Arm arches should use 'makepkg -A' build command to ignore list of supported archtectures?

Hey :-),

does your package handle caching for multiple arches (arm and x8664)? Cheers

This builds just fine on arm so I think it's safe to add at least armv7h (which is what I tested it on)