On Sat, Aug 10, 2019 at 6:12 AM Mattia Rizzolo <mat...@debian.org> wrote:
> On Mon, Dec 24, 2018 at 08:44:25AM -0300, Felipe Sateler wrote: > > > > Perhaps znc could Provide: znc-plugin-$somenumber, which could be > used by > > > > out-of-tree plugins? Adding the znc maintainers to the loop for their > > > input > > > > > > That's being used successfully by some packages ... > > > > > > > I'm creating a new bug for tracking this (better) solution. > > ivodd proposed the other day on #-relase to instead have these type of > plugins embedded in src:znc. > > I'm also extremely interested in this as, following on the shoes of > znc-backlog, I've packaged znc-push. > > znc-backlog is a single 253 lines file, whereas znc-push is ~2000 lines. > Both change very rarely, so I think it would be feasible to just put > both of them within src:znc's debian/ and build them from there. Then > put them in separate binary packages, with the description explicitly > saying they are contrib modules. > I'll also be happy to help out with the maintenance of these parts if > you'd like to, not to mention provide a full patch. > /me wonders why are we pushing manual work to developers when all it takes to fix this problem is to automatically rebuild reverse dependencies on new uploads. Don't we have a solution for this already? How do go or haskell packages do this? -- Saludos, Felipe Sateler
