Hello all.
While working on Qt/KDE bindings (some KDE apps are build upon them, so I
could not cheat and "forget" them, leaving porting for someone else :) ),
I've seen many sample scripts that has "#!/usr/bin/env some-interpreter"
shebangs. They are easily updated via MODXYZ_ADJ_FILES, but do we need
this at all? The point is that those examples are intended for novice
programmers and therefore focus on portability for a reason. I fix such
shebangs for "worker" ones, but not sure about examples/tutorials/samples
etc.
Also, is there is a point in creating packages like "python-run",
containing single symlink to default python as "bin/python" in PLIST and
such Python version as dependency? I.e.:
PKGNAME=python-run
MODULES=lang/python
NO_BUILD=Yes
do-install:
ln -sf ${MODPY_BIN} ${PREFIX}/bin/python
I will provide diffs if anyone is interested in one or another solution.
(And all this definitely should be covered in porting guide...)
--
WBR,
Vadim Zhukov
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
