* Vern Sun <[email protected]>, 2013-03-25, 00:35:
4. python modules, private / public
Are Python modules included by this package supposed to by used by
other software?
I don't think so.
Otherwise, they should be moved to a private directory.
Does this meaning to use `/usr/share/foo` to instead of
`/usr/share/pyshared/foo` look like below:
- /usr/share/pyshared/foo:
./usr/share/pyshared/ranger/api/commands.py
...
./usr/lib/python2.6/dist-packages/ranger/api/commands.py ->
../../../../../share/pyshared/ranger/api/commands.py
...
./usr/lib/python2.7/dist-packages/ranger/api/commands.py ->
../../../../../share/pyshared/ranger/api/commands.py
...
- /usr/share/foo:
./usr/share/ranger/api/commands.py
...
./usr/lib/python2.6/dist-packages/ranger/api/commands.py ->
../../../../../share/ranger/api/commands.py
...
./usr/lib/python2.7/dist-packages/ranger/api/commands.py ->
../../../../../share/ranger/api/commands.py
...
No, that would be incorrect.
The whole point of moving the modules to a private directory is to make
them unavailable for import to other software. Adding symlinks pointing
from dist-package to the private directory would defeat this purpose.
10. upstream /tmp => $TMPDIR [^2]
fixed
If TMPDIR is unset, you should fall back to /tmp.
What about security? See last paragraphs of Policy ยง10.4.
--
Jakub Wilk
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive: http://lists.debian.org/[email protected]
