Tracking of pkgbases across repositories
To allow our build tooling to evolve in the future, we will need to support scenarios in which a pkgbase
may span several repositories.
As an example: Build foo
and lib32-foo
(where the former is e.g. part of [core]
while the latter is part of [multilib]
) from the same PKGBUILD
In the current setup pkgbases exist only per repository (represented by OutputPackageBase
and OutputPackage
).
A possible solution to this issue could be to provide the same OutputPackageBase
with differing OutputPackage
children, where we somehow point at the other relevant bit. This would only duplicate the data required for OutputPackageBase
and allow us to separate the OutputPackage
instances.
In a way this is already now possible by just importing the given subset of packages to the respective target repositories. Keeping track of them when upgrading (e.g. to not lose sync between the two packages in their repositories) is a bit more difficult though, so a dedicated mechanism is likely warranted here.