From: Roger B. <ro...@ro...> - 2004-05-11 23:24:30
|
Stephen Wood wrote: > OK, the problem was that the last p_sanyonewer.py that I checked in > ended up being a null file. Any idea how that happened? (I am also curious as to why you get a CRC error since such checking should happen before > Roger, can you do a new build? It will keep the noise level on the > lists from being to high for the next two weeks. Steven, can you redo the Mac build? > Can we do something reduce the problems of out of date p_*.py files, or > even elinate them from the CVS? The reason they are in CVS is so that we can get back exactly an earlier release. Whenever you have "built" files, and don't save them, it can get quite difficult knowing what went on. Also rebuilding them automatically could also result in unintentional differences. Arguably I am being overly cautious, but I wanted to be in a situation where I know for sure that the Mac, Linux and Windows builds are all using exactly the same code. I had also hoped that having the releases available for day to bitpim-devel folks would mean they get some double checking. Roger |