Bugzilla Bug 23998

I'm emerging bacula 1.31 with the "static" USE flag, but when the emerging is
done, the resulting binaries as dynamic binaries. Heres the why:

The guys from bacula as handling static compilation in a kind of an odd way (at
least odd to me). When the static parameters are added to the configure script,
and then make is runned, make willl create both the dynamic and the static
binaries. So (e.g.) on will be called bacula-fd (witch is the dynamic one) and
the other will be called static-bacula-fd. When make install occurs, it will
install bacula-fd instead of static-bacula-fd.

I still haven't checked if this issue is handled diferently on bacula's CVS, but
I will report this as a bug to them. In the meen time, I think this issue sould
be workarrounded.

I'm not mutch of a gentoo hacker myself (so I'm sorry if this is not the proper
way to do it), but I'll suggest adding another "use static" after the make
install takes place, that will copy the proper binaries on the apropiate places.

has Kern fixed the Bacula Makefiles for this yet?  Any idea?

SOrry, I cant maintain this.

This has been fixed for 1.32f and 1.32f-5. Please try those ebuilds.