On Mon, Aug 19, 2019, 11:04 Mattia Rizzolo wrote:
> Hi Felipe,
>
> On Sun, Aug 11, 2019 at 07:23:24PM -0400, Felipe Sateler wrote:
> > > 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
> > >
Hi Felipe,
On Sun, Aug 11, 2019 at 07:23:24PM -0400, Felipe Sateler wrote:
> > 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.
Am 10.08.2019 um 12:12 schrieb Mattia Rizzolo:
> 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
On Sun, Aug 11, 2019 at 07:23:24PM -0400, Felipe Sateler wrote:
> /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
>
On Sat, Aug 10, 2019 at 6:12 AM Mattia Rizzolo 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
>
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 ...
> >
>
>
6 matches
Mail list logo
