On Fri, Dec 28, 2018 at 10:33 AM Patrick Matthäi <pmatth...@debian.org> wrote:
> Hola, > Am 24.12.2018 um 12:44 schrieb Felipe Sateler: > > > 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. > > > I dont know how this would help now after the relaxed dependency from > znc-backlog, because..: > > * on changes znc-backlog still needs a binNMU or code changes, like now > Right. But the current solution is still suboptimal. For example, if you upload a new package changing only metadata (say, the Vcs-* fields), znc-backlog would need a binNMU. In the more general case, a new upstream version of znc might not break the plugin ABI. > * I can provide a znc-plugin-$foobar package, but who ensures at an non > stable api, if a change is necessary or not? I think it will make it more > complicated or is there a nice solution for it? > Indeed, this implies a lot more work for you. -- Saludos, Felipe Sateler
