[build_scripts] executable
Hi all, I'm working on some system packages for http://nslu2-linux.org optware with setuptools (svn dev so I can use the --single-version-externally-managed). Thanks to your hard work, so far it looks very promising. However, since the platform I'm working on requires cross build, the python on debian host /usr/bin/python2.4 should not be used for scripts in the package. In particular we need all scripts in the package to have #!/opt/bin/python As the first line. With traditional distutils, we can append the following to setup.cfg [build_scripts] executable=/opt/bin/python Can we add that back please? Thanks, -Brian Zhou
Never mind. I think it's problem of the way turbogears uses setuptools, in the case of sqlobject for example, it works ok. -Brian Zhou On 12/26/05, Brian Zhou <b88zhou@gmail.com> wrote:
Hi all,
I'm working on some system packages for http://nslu2-linux.org optware with setuptools (svn dev so I can use the --single-version-externally-managed). Thanks to your hard work, so far it looks very promising.
However, since the platform I'm working on requires cross build, the python on debian host /usr/bin/python2.4 should not be used for scripts in the package. In particular we need all scripts in the package to have
#!/opt/bin/python
As the first line. With traditional distutils, we can append the following to setup.cfg
[build_scripts] executable=/opt/bin/python
Can we add that back please?
Thanks,
-Brian Zhou
participants (1)
-
Brian Zhou