Share YAY cache

burny02 · 2024-08-12 13:48:50

Hi

I've recently installed nginx to be able to share pacman installations between 3 or my machines.

This works nicely

I was wondering if there was a way to do something similar to avoid rebuilding of yay packages?

I tried changing the build directory

yay --builddir /mnt/NAS/Fast/yay-cache --save

But it seems to be slow when trying to install from another machine - Slower than installing directly (although it doesn't download anything)

In the example I am trying for example; it is still extracting the deb, generating the PKGINFO etc, compressing package

Any ideas?

Thanks in advance

Trilby · 2024-08-12 13:53:56

Why would you want the build directory on the NAS? Just put the built packages in a custom repo on the NAS, then just install them with pacman.

You might be interested in Alad's helper (I always forget the name, aur-utils, or aur-tools, or similar) as it makes this easier than yay.

burny02 · 2024-08-12 13:56:00

I'm not particularly clued into what is the best way to do this.

I assumed putting the cache and telling yay to NOT rebuild would give that expected outcome, i.e. not having to rebuild for 3 machines

seth · 2024-08-12 16:17:30

You're downloading the deb into the nas, read it from there to decompress it onto the NAS, then read it from there again to tar/compress it into the arch package on the NAS, ie. you're causing a lot of network filesystem traffic.

You only want to set PKGDEST, https://man.archlinux.org/man/core/pacm … .conf.5.en

burny02 · 2024-08-12 17:02:31

I want to do this for all my yay components, i.e. lots of software across multiple computers

Is the only way to do this - Using pacman to install the files individually from that cache ? (.tar.zst/tar.xz that is created by the first machine)

Last edited by burny02 (2024-08-12 17:02:49)

Trilby · 2024-08-12 18:21:12

What other way would you want? Pacman is the only way to install packages on any arch system. In the build directory you can also use `makepkg -i` but if the package is already built, this really does nothing but hand it off to `pacman -U ...` anyways.

burny02 · 2024-08-12 18:26:33

I'd like to be able to reuse my yay builds across multiple pc without having to rebuild them, or without having to manually specify each package with pacman -U - Ideally!

Trilby · 2024-08-12 18:44:26

What's wrong with `pacman -U ...`? How would you prefer to specify which packages should be installed on each system? If you create a custom repo on the NAS you can just install them with `pacman -S <pkgname>` so you wouldn't need the full path. But I'm not sure that'd really be that different for the initial install. The benefit of the custom repo is then newly built versions posted to the repo on your NAS will get included in regular system updates for all the other machines (so your regular `pacman -Syu` will upgrade any of these packages).

Last edited by Trilby (2024-08-12 18:53:22)

Lone_Wolf · 2024-08-12 19:03:57

I'd like to be able to reuse my yay builds across multiple pc without having to rebuild them, or without having to manually specify each package with pacman -U - Ideally!

There is no such thing as yay builds .
yay is a pacman wrapper that internally uses pacman & makepkg to install/build stuff .

Create a custom repo for aur packages, add it to your pacman.conf and your nginx server.
Then you can use pacman or your favorite-tool-that-uses-pacman-under-the-hood to access all those packages.

seth · 2024-08-12 19:50:51

Your problem is

man yay wrote:

--builddir <dir>
Directory to use for Building AUR Packages. This directory is also used as the AUR
cache when deciding if Yay should skip builds.

so w/ yay you cannot (from what I can tell) split build and storage dir and you absolutely don't want to *build* on the NAS.
So this is a dead end.
You can still locally build using yay and distribute the packges from the NAS using a local repo or you can abandon yay and allow makepkg to locally build a package but use the nas as storage (so that as long as you don't force rebuilds, makepkg on any system will benefit from the pre-build packages of every other system)
There is no "I just use yay over the NAS that that's also gonna perform well".

burny02 · 2024-08-12 21:09:21

I just tried the custom repo route.

I think this is dead - It's more effort than it is worth, to build locally and then think about which may or not be needed and then move them over individually

At least the pacman nginx caching works very well without any input

bulletmark · 2024-08-12 22:02:45

This may be of interest: https://github.com/bulletmark/pacpush

Trilby · 2024-08-13 00:13:10

burny02 wrote:

I just tried the custom repo route... It's more effort than it is worth

That's why I suggested this:

Trilby wrote:

You might be interested in Alad's helper (I always forget the name, aur-utils, or aur-tools, or similar) as it makes this easier than yay.

burny02 · 2024-08-13 09:34:04

Just tried this method

Don't particularly like it to be honest, again more effort than it is worth

It's still very manual in conjunction with yay, and would work better if one computer was the 'master' where all the building happens etc (This isn't the case)
It does seem like a very useful tool, though

WorMzy · 2024-08-13 10:37:43

Mod note: moving to AUR Issues.

Arch Linux

#1 2024-08-12 13:48:50

Share YAY cache

#2 2024-08-12 13:53:56

Re: Share YAY cache

#3 2024-08-12 13:56:00

Re: Share YAY cache

#4 2024-08-12 16:17:30

Re: Share YAY cache

#5 2024-08-12 17:02:31

Re: Share YAY cache

#6 2024-08-12 18:21:12

Re: Share YAY cache

#7 2024-08-12 18:26:33

Re: Share YAY cache

#8 2024-08-12 18:44:26

Re: Share YAY cache

#9 2024-08-12 19:03:57

Re: Share YAY cache

#10 2024-08-12 19:50:51

Re: Share YAY cache

#11 2024-08-12 21:09:21

Re: Share YAY cache

#12 2024-08-12 22:02:45

Re: Share YAY cache

#13 2024-08-13 00:13:10

Re: Share YAY cache

#14 2024-08-13 09:34:04

Re: Share YAY cache

#15 2024-08-13 10:37:43

Re: Share YAY cache

Board footer