On Tue, Jun 15, 2010 at 3:13 PM, "Martin v. Löwis" wrote:

...

I am interested in adding some metadata in the installers generated by bdist_wininst. I did it through a hack: base64-encoding the medata in a new section in the embedded cfgdata. From my understanding the installer.c sources, this seems safe, and the generated installer does work, but I am wondering whether there is a better way of doing it, and whether it could potentially breaks something,

Why not use a file that gets installed in the system?

Because I don't want the file installed. I am interested in doing this for arbitrary packages (the goal is to add support for egg <-> windows installer conversion in my packaging solution) David

On Tue, Jun 15, 2010 at 3:39 PM, "Martin v. Löwis" wrote:

Am 15.06.2010 08:23, schrieb David Cournapeau:

...

On Tue, Jun 15, 2010 at 3:13 PM, "Martin v. Löwis"  wrote:

...

...

I am interested in adding some metadata in the installers generated by bdist_wininst. I did it through a hack: base64-encoding the medata in a new section in the embedded cfgdata. From my understanding the installer.c sources, this seems safe, and the generated installer does work, but I am wondering whether there is a better way of doing it, and whether it could potentially breaks something,

Why not use a file that gets installed in the system?

Because I don't want the file installed. I am interested in doing this for arbitrary packages (the goal is to add support for egg<->  windows installer conversion in my packaging solution)

Ah. I would then add a prefix META to the scheme, and modify bdist_wininst to skip all files with that prefix.

I did not want to go that road because of the need to recompile bdist_wininst for all python versions, but maybe that's the best solution. Do you think it would make sense to do it for python itself proper (in distutils), so that different implementations could put whatever they want there for their purpose ? cheers, David