On Thu, Jul 11, 2019 at 10:23:59PM -0300, Chris Lamb wrote:
> Hi Julian,
>
> > I was just thinking that adding deprecation warnings and stuff
> > to software is "nice", but the problem with warnings is that they
> > tend to not break tests.
>
> I'm guessing you have a particular package or use-ca
Hi Simon,
> > Hm, although perhaps DEB_BUILD_OPTIONS is the prefered place for this
> > kind of toggle rather than an environment variable?
>
> We already have "nocheck" to disable tests, and IMO the default should be
> to run tests if we can.
Unless I am grossly misunderstanding him, Julian's s
Hi,
On Thu, Jul 11, 2019 at 10:23:59PM -0300, Chris Lamb wrote:
> > I feel like it would be nice to come up with a standard environment
> > variable to turn warnings into errors, so we can ensure issues are
> > fixed and the warnings are actually useful.
> Hm, although perhaps DEB_BUILD_OPTIONS
[adding jak@ to CC as requested; no need to CC me, however...]
Hi Julian,
> I was just thinking that adding deprecation warnings and stuff
> to software is "nice", but the problem with warnings is that they
> tend to not break tests.
I'm guessing you have a particular package or use-case in mind
Dear fellow developers,
I was just thinking that adding deprecation warnings and stuff
to software is "nice", but the problem with warnings is that they
tend to not break tests.
I feel like it would be nice to come up with a standard environment
variable to turn warnings into errors, so we can en
5 matches
Mail list logo
