Re: Git checkout/clean and double-buildability.

2013-05-05 Thread Adam Borowski
On Sun, May 05, 2013 at 04:30:05AM +0200, Lucas Nussbaum wrote: > On 05/05/13 at 03:06 +0200, Adam Borowski wrote: > > On Sun, May 05, 2013 at 10:00:07AM +0900, Charles Plessy wrote: > > > Anyway, given that our infrastructure builds binary packages from a fresh > > > unpacked source package, I wou

Re: Git checkout/clean and double-buildability.

2013-05-04 Thread Lucas Nussbaum
On 05/05/13 at 03:06 +0200, Adam Borowski wrote: > On Sun, May 05, 2013 at 10:00:07AM +0900, Charles Plessy wrote: > > Anyway, given that our infrastructure builds binary packages from a fresh > > unpacked source package, I would prefer if we keep the compromise that > > imperfect "clean" targets a

Re: Git checkout/clean and double-buildability.

2013-05-04 Thread Adam Borowski
On Sun, May 05, 2013 at 10:00:07AM +0900, Charles Plessy wrote: > Anyway, given that our infrastructure builds binary packages from a fresh > unpacked source package, I would prefer if we keep the compromise that > imperfect "clean" targets are not release-critical problems. Note that for a big ma

Git checkout/clean and double-buildability.

2013-05-04 Thread Charles Plessy
Le Sat, May 04, 2013 at 03:25:34PM +0200, Lucas Nussbaum a écrit : > > Now, I'm not so sure that we should spend developer time to (1) find > those issues and file bugs; (2) fix those issues. I personally find it > easier to create a temporary git repository and to use git clean / git > checkout t