Bugzilla Bug 111057

siege.config installed by app-benchmarks/siege-2.61 reports that it creates a
default .siegerc file for you 
in your home directory.

When executed, siege.config creates an empty ~/.siegerc, and then (incorrectly)
outputs the contents of 
the default file to the console (stdout).  It ought to place the contents in
~/.siegerc

If siege.config is then run again, it sees the empty ~/.siegerc and tells you
that to go edit the sample 
parameters  of the empty file.

Upon further investigation, the config file is output to stderr.  A workaround
that worked for me was:

siege.config 2> tempfile
mv tempfile ~/.siegerc

The problem is that bash is interpreting some of the things after the cat >
$rcfile <<_EOF_ like the '${}' (causing a bad substitution error) and the
'$(HOME)' (causing a 'HOME: command not found' error) so the contents are being
sent to stderr instead of $rcfile.  I've added some sedfu to the ebuild so that
those get escaped and thus not interpreted by bash.

Can you please report this problem upstream as well?

Reported this bug upstream to Jeff Fulmer