Message86853
I'm still stuck on getting the right name to show up in ARP.
Another problem: it seems like we have to update the ProductCode at
runtime as well - otherwise, you can only have one module installed for
all the versions of Python you have on your machine. But if we generate
a new GUID at runtime, how do we make sure that the GUID for moduleXXX +
Python 2.6 is the same every time (as it should be for the MSI to
recognize when a product is being removed, reinstalled, etc.)
Thoughts? Is there a way to deterministically generate a GUID for each
Python version? (Note that it doesn't make sense to do this ahead of
time - an installer created for Python 3.1 should work with Python 3.2
as well.) |
|
Date |
User |
Action |
Args |
2009-04-30 19:09:38 | bethard | set | recipients:
+ bethard, loewis, tarek |
2009-04-30 19:09:38 | bethard | set | messageid: <1241118578.01.0.855287652423.issue5311@psf.upfronthosting.co.za> |
2009-04-30 19:09:36 | bethard | link | issue5311 messages |
2009-04-30 19:09:36 | bethard | create | |
|