A small update on the workings of this script:
I found out that for example:
#!/usr/bin/env awk -f
doesn't work as the shell (bash and tcsh) seem to split on the first
space, and passes "awk -f" as argument to env, which in turn doesn't
find a command called "awk -f".
I haven't found a solution for this problem yet, but I think that
/usr/bin/env is not the solution to our problem here. We either need to
write our own version of 'env' that does what we want, or maybe find our
way through another program, perhaps a shell like /bin/sh. (I think we
need to keep it portable...)
> Brian Harring wrote:
>>> The problem with these kinds of scripts is that their portability is
>>> not really assured. I dubbed whether I would write a quick C
>>> version, but again I stumbled upon the portability question and
>>> decided not to do so, because portage, as inner core of Gentoo,
>>> should be as much as possible unaffected by environmental
>>> differences. Python is (like Java) a solution to that. So,
>>> ultimately, this script should be rewritten in Python.
>> module, not script is prefered.
> As I said, I'm a python illiterate :)
>> Assuming I actually finish triggers and they don't suck, it'll be a
>> passing the func in, not exec'ing a strict.
> hmmm... sounds good. For my understanding, does it mean that the func
> could be executed based on (trigger) conditions, like ppc-macos or
> PREFIX != "/", pref.userWantsSheBang == True or something like that?
Gentoo for Mac OS X
firstname.lastname@example.org mailing list