2010-09-24 12:42:23 |
Olivier Naudan |
description |
In case the file modification dates are all equals (as in a GIT tree), debian/control might not be re-generated even if debian/control.in was modified. Same thing for debian/build-deps and debian/build-deps.in.
To be on the safe side, I suggest to touch the .in files to force a re-generation, independently of timestamps.
Also I would add a warning notice in debian/control and debian/build-dep, stating that it is generated and shall not be modified. |
In case the file modification dates are all equals (as in a GIT tree), debian/control might not be re-generated even if debian/control.in was modified. Same thing for debian/build-deps and debian/build-deps.in.
To be on the safe side, I suggest to touch the .in files to force a re-generation, independently of timestamps.
Also I would add a warning notice in debian/control and debian/build-dep, stating that it is generated and shall not be modified.
|
|