On Sat, Feb 6, 2010 at 5:33 AM, P.J. Eby
At 06:10 PM 2/5/2010 -0800, Sridhar Ratnakumar wrote:
On 2010-02-05, at 4:57 PM, P.J. Eby wrote:
At 04:49 PM 2/5/2010 -0800, Sridhar Ratnakumar wrote:
Do we have a real-world example for installing uninstallable data files outside sys.prefix?
Scripts aren't always in sys.prefix,
Scripts *usually* go to sys.prefix/bin (or sys.prefix/Scripts or site.USER_BASE/Scripts). Are their packages that actually put them elsewhere?
It's not the package that determines installation locations, it's the user's command line options and configuration file settings that determine the locations for libraries, scripts, and data files.
IOW some paths in the PREFIXES file (or the RECORD file as long as we are able to find-and-replace paths in there) *need* to be updated at installation time no matter what we decide to do here. So, it seems to me that we need to keep unexpanded paths [1] in the RECORD file and let the install command expand them using installation option . But we have to avoid this expansion when doing binary releases. It seems feasible to me in both cases. And Wolojda could work later on adding more paths definitions and how to configure them through distutils options. [1] See _INSTALL_SCHEME in http://svn.python.org/view/python/trunk/Lib/sysconfig.py?view=markup that can be read through API (expanded or unexpanded) Regards Tarek -- Tarek Ziadé | http://ziade.org