|
From: Hans-Bernhard B. <HBB...@t-...> - 2011-02-16 23:38:22
|
On 16.02.2011 11:07, Mojca Miklavec wrote: > It seems that ./configure script was old indeed That's not really supposed to happen. There's code in the Makefiles that automatically builds everything, _including_ configure itself, whenever any of the files it's made from change. So unless you lack auto tools, configure shouldn't acquire bit rot like that. > Out of curiosity: is there any reason why "configure" script is not > included in CVS? Because no generated files are supposed to be. Source control is for holding source files, not generates. > but would be easier for the end users.) End users are not supposed to be running off CVS directly in the first place. Those who decide they want to anyway pay a price: they will need some extra tools, and the skills to use them. > On the other hand, there are two files, > config/djconfig.sh > missing > which are constantly displayed as being present in repository, but > they keep changing when I run ./prepare (maybe also on other > occasions, for example when running configure or make, I'm not sure). > > However I checked again and it seems that only executable bit is changed. And that's because CVS is lousy at managing the permission bits of working files. The chmod is the only way we know to make sure you get exactly the permissions you need. > In short: I would like to suggest to add "configure" script to > repository and/or at least add executable bit to the two files > mentioned above. If only that were possible in a reliable fashion. |