On Thu, Apr 17, 2014 at 07:08:30PM +0200, Jonas Smedegaard wrote: > If we decide dh-autoreconf is the way forward, that is. > > Personally I would then silence the lintian warning, because... > > a) I dislike dh-autoreconf: It removes changed files which breaks my > workflow where disappearing files are treated as an error. >
Yes, I know, that's slightly unfortunate in some cases; especially in cases where files are only updated if they already exist. I thought about adding a support for hardlinking the tree to somewhere else, but this will most likely break due to shell scripts not doing atomic replace AFAIK. Copying the files as a backup and restoring is a nice option, but one that requires to much I/O during the build, especially on the larger packages. A sane think would be cp with reflinks, but since not everyone uses btrfs for buildds, this does not make sense. Open to other suggestions, but you might want to CC me, I only read and post to debian-devel sometimes, using gmane with mutt's semi-working nntp patch. -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. Please do not top-post if possible. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140422202210.GB15264@jak-x230
