Re: Cleaning up after 'gbp buildpackage'
On Sun, 08 Jul 2018, Daniele Nicolodi wrote:
> On 08/07/2018 19:28, Henrique de Moraes Holschuh wrote:
> > On Sun, 08 Jul 2018, Daniele Nicolodi wrote:
> >> After a successful package build done with 'gbp buildpackage' the
> >> package directory is left in a state which requires to run 'debuild --
> >> clean' before being able to build the package again.
> >
> > Packages must be buildable several times in a row *without* the need to
> > *manually* call the clean target.
> >
> > If it needs intermediate cleaning, arrange for it to detect and do so
> > automatically.
>
> The package builds just fine without intermediated cleaning, it is just
> gbp that complains about uncommitted changes to the source tree. That's
I see. Yeah, that's gbp trying too hard to protect you from yourself :(
You can, of course, configure it to never warn, but then you lose that
last line of defense.
--
Henrique Holschuh
Reply to: