I'm not sure that's a good idea.

Sharing CacheDir makes sense, because all of the files there are owned by root. However, SRCDEST is owned by a normal user outside of the chroot, and sort-of root and sort-of "nobody" inside of the chroot. We could chown the files when done, but if there were an error and we had to bail early that wouldn't happen. I think it makes more sense to copy the files from the chroots's SRCDEST to the outside SRCDEST and chown them at once.

dirty hack: make "nobody" on chroot have the same uid as the packager's user (most probably 1000) or better, create a 'packager' user on the chroot with the same said logic :)

then run chroot tools as this user

Do we need SRCDEST to be owned by the normal user? I nearly never need to modify them.

mtjm: yes, not to modify them manually, but so that tools can (normal makepkg, librestage, librerelease)

I'm removing this from the "don't break and confuse parabolers" target; I'm happy with how copying works, and like I said, I'm not sure this is a good idea. I'm leaving it open as a "wish", in case we ever want to revisit it.

Upstream makechrootpkg does this; sort of. It bind mounts them to srcdest_host and pkgdest_host, then symlinks the files, then copies the new files to *_host when done.

We'll get that the next time I merge devtools updates.

Having upgraded to the new devtools, it now does this (as explained in my previous comment).