^maybe it would be a bit more compact to use the pkgname to depend on it instead of these long paths :)

MASTER_SITES=        SF/${THEME:tW:tl:S/ /-/g}

Never use MASTER_SITE_SUBDIR.

Updated.
Should MASTER_SITE_SUBDIR be renamed into _MASTER_SITE_SUBDIR then in Mk/?

How to do this?

For example, RUN_DEPENDS=gtk-murrine-engine:x11-themes/gtk-murrine-engine doesn't work.

|Porters Handbook

A minimal version of a dependency can be specified in any *_DEPENDS except LIB_DEPENDS using this syntax:

p5-Spiffy>=0.26:devel/p5-Spiffy

The first field contains a dependent package name, which must match the entry in the package database, a comparison sign, and a package version. The > dependency is satisfied if p5-Spiffy-0.26 or newer is installed on the machine.

I grant you it's nicer to depend on a file, but these paths just look too long and subject o change :D

This didn't occur to me fast enough. -)

^out of curiousity. Have you checked whether they are really not requiring any bash features?

-) Of course I did. They are all very simple and plain scripts.

No, it reuses the THEME variable.
Would you prefer to just type the text instead?

well, the punchline is on line 3, isn't it?

very good :)

^ I think you could come up with something nicer here
a) is it really important to get rid of the whitespaces?
b) you only want to replace the whitepsaces in "Xfce Theme <Foo>", so maybe iterate over the Foo's you want to install and do a ${COPYTREE_SHARE} "Xfce Theme ${FOO}" ${STAGEDIR}${PREFIX}/share/themes/Xfce-Theme-${FOO}"
or some valid variation thereof.

Which might look a bit cleaner.

I simplified it. -)

I am definitely laughing!

Is the subdir likely to change? If not, it's probably safe to hardcode it.

Just FYI, if you wanted to, you could also use shebangfix here, which is very precise about how it modifies files.

USES=shebangfix
SHEBANG_REGEX= 00.[0-4]0
bash_CMD=/bin/sh