2009/7/7 Paul Moore <p.f.mo...@gmail.com>: > 2009/7/6 P.J. Eby <p...@telecommunity.com>: >> At 07:38 PM 7/6/2009 +0100, Paul Moore wrote: >>> >>> As promised, here are some open questions on PEP 376. >>> >>> - Will the public API names be changed from *egginfo* to *metadata*? >> >> +1 (FWIW, 'metadata' is what pkg_resources API refers to this kind of stuff >> as.) > > Thanks. I think this one is pretty non-controversial.
+1, I'll change the PEP accordingly; >>> - How will bdist_wininst/bdist_msi/bdist_rpm be updated? >> >> bdist_wininst, bdist_dumb, and various others use 'install --root' pattern >> to generate files for installation, which means that they would >> transparently end up writing a correct RECORD file, except for the inclusion >> of incorrect absolute paths for non-libdir-relative files. However, if we >> used the "all relative in RECORD, with a base in INSTALLER", these cases >> could transparently be treated as another instance of install directory >> relocation. >> >> I don't know if bdist_msi does a --root install before generating the .msi; >> if it does, then it should work the same way. > > Yes, that sounds like a plausible approach. As I said earlier in the previous thread, all these commands rely on a call to the install command, so bdist_msi does too. _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com