Define relationship with source repositories for deriving a package's repository
In a setup where the sources for each pkgbase are kept in a git repository each, we need to figure out, what the relationship between this application (or dbscripts for that matter) will be.
Having repository based grouping for pkgbases (e.g. /core/pacman
) in a VCS forge such as gitlab can have the upside for us to derive the target location of a given set of packages in the binary package repository.
When thinking of a potential bootstrap scenario, where we initialize a given package source repository in a group (e.g. /foo/bar
) we can upon trying to push packages - built from that particular pkgbase - towards the binary repository management software (such as arch-repo-management or dbscripts) derive the target from its remote link (e.g. https://gitlab.archlinux.org/packages/foo/bar
-> repository => foo, pkgbase => bar).
This type of scenario would allow easy detection of target location (which is paired with an ACL of the application that checks whether the given user is allowed to do this operation). However, at this point in time the workflow around this is yet to be defined and needs discussion.