It looks like msi has some rules about file replacing files intended to make it so it doesn't replace stuff modified by the user and doesn't replace user's files that are newer than what's being installed - here's a random page written by some random person that seems to describe them: http://juice.altiris.com/tip/3923/how-files-are-overwritten-windows-installer-service
I think the SDL files would be considered versioned, and none of the pygame files would be considered versioned. ...It seems we'd want to completely turn that behavior off... if I installed pygame 1.7 for instance, I'd expect it to clobber 1.8, it's my own choice to downgrade - but the default behavior of msi is to successfully "install" but then do nothing evidentally there is some "REINSTALLMODE" property that controls this stuff - I guess the default is "omus" where the o means replace older only. I guess we'd want "amus" where a means to replace all files. Here's another random page about that: http://juice.altiris.com/tip/2904/controlling-file-version-settings .... so provided that's all right - the next obstacle would be customizing something with bdist_msi... does anybody know how we might change a "property" when using bdist_msi? or maybe how to change properties after creating the file? On Wed, May 21, 2008 at 10:20 PM, Lenard Lindstrom <[EMAIL PROTECTED]> wrote: > When I try this for Python 2.4 I find nothing is replaced. Only files new > to Pygame 1.8 are added. Consequently I don't get the error since it is > still effectively Pygame 1.7. The msi installer is generated entirely by > distutils. To customize its behavior means more hacks to distutils. We could > always go back to the distutils executable Windows installer. What I know is > msi is demanding. You must design your project around it for it to work as > intended. Also the msi module included with Python 2.5 is inflexible. > > Lenard > > > Brian Fisher wrote: > >> So does anybody know why exactly this problem happens? Is there some file >> left behind by 1.7.1 that is not replaced with a 1.8.0 file? If so, what >> file? >> >> On Wed, May 21, 2008 at 4:12 PM, René Dudfield <[EMAIL PROTECTED] <mailto: >> [EMAIL PROTECTED]>> wrote: >> >> hey, >> >> I've made a note about uninstalling pygame 1.7.1 first on the >> download page... >> >> However I think we need to figure out how to get the windows installer >> to check if pygame is installed already... and if so uninstall it. Or >> if we can't do that, make it display instructions to uninstall in the >> installer (maybe by putting it in the README). >> >> >
