I think that's a great idea and in fact I've been working on an integration with apkg the automation packaging tool I'm developing in order to allow easy packaging - you can see the changes here in my branch:
https://gitlab.nic.cz/jruzicka/bird/-/tree/apkg A single new distro/ directory includes: * distro/pkg/deb: .deb package template from Debian * distro/pkg/rpm: rpm package template from Fedora * distro/script/make-obs.sh: use apkg to create OBS source package With these changes (not final) as well as some apkg fixes related to bird vs bird2 anyone will be able to build packages directly from project repo as well as from project archives(tarblls) with a simple command: apkg build You can see more info about apkg in docs: https://apkg.rtfd.io I don't want to hype that before it's complete but is should be fairly sweet. Cheers, Jakub Ružička On 4/9/21 5:12 AM, Ondrej Zajicek wrote: > On Fri, Apr 09, 2021 at 04:55:15AM +0200, Jakub Ružička wrote: >> Hello, >> >> I've been recently tasked with updating Debian and Ubuntu bird packages >> and I'm probably going to maintain all bird packaging (including Debian >> downstream) from now on as I do with Knot DNS and Knot Resolver packages > Hello > > Welcome. That is great, hopefully we will have more streamlined process > with new packages. What do you think about moving some Debian (and other > distros') package-related data (e.g. debian/* files) from downstream > (e.g. salsa.debian.org) directly to our bird git repository? Seems to > me that if upstream (we) also publishes Debian packages, it would make > sense these packages should be buildable using just data from upstream. >
