We currently use OBS for building and publishing APT packages for the Apertis project (a Debian derivative distribution).
At the moment we use downstream patches for the publisher (src/backend/bs_publish) in order to use reprepro instead of dpkg-scanpackages/dpkg-scansources.
As we're considering implementing a new APT publisher based on aptly, we'd like to do so in a way that can be upstreamed to OBS so it can benefit the whole community. This obviously raises several questions as to how we should proceed, so I'm sending this email as a call for advice/comments/suggestions.
We're considering the following: - this new publisher would be implemented in addition to the existing dpkg-scan* based one and be selectable through global configuration options. - using aptly opens up possibilities, but it isn't always as straightforward as a few system() call; we would therefore need to either ship a helper tool or add a new BSPublisher submodule (the latter is the preferred option atm) - aptly can also be used through a REST API, which implies some asynchronous processing would be preferrable. Is there currently a way to handle async processing in OBS, or would that require another helper tool/module, if possible at all?
We're only at the planning and design stage for now, so we would be very interested in your opinion and comments regarding the above.