Jakub Wilk writes:
> * Ben Finney , 2013-09-09, 13:36:
> > * Use ‘.links’ to make a symlink for each package to
> > ‘usr/share//foofile’ at
> > ‘usr/lib/python${PYTHON_VERSION}/dist-packages/${DISTRIBUTION_NAME}/foofile’.
>
> How can you do that without hardcoding Python version?
By relying on t
[Jakub Wilk, 2013-09-09]
> * Ben Finney , 2013-09-09, 13:36:
> >* Use ‘.links’ to make a symlink for each package to
> >‘usr/share//foofile’ at
> >‘usr/lib/python${PYTHON_VERSION}/dist-packages/${DISTRIBUTION_NAME}/foofile’.
>
> How can you do that without hardcoding Python version?
should I add
* Ben Finney , 2013-09-09, 13:36:
* Use ‘.links’ to make a symlink for each package to
‘usr/share//foofile’ at
‘usr/lib/python${PYTHON_VERSION}/dist-packages/${DISTRIBUTION_NAME}/foofile’.
How can you do that without hardcoding Python version?
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debia
Ben Finney writes:
> In that case, I currently have no good solution. I had hoped to use
> some Python standard-library resource access function to find the
> files wherever they are installed.
I have hacked a work-around:
* Patch the ‘MANIFEST.in’ and ‘setup.py’ to omit all mention of the
re
4 matches
Mail list logo