As a consequence of bug #87972, this ebuild was redesigned to suggest the use of MBROLA via the appropriate use flag (mbrola). If this flag is used, then MBROLA becomes a dependency, and the Festival part of MBROLA voices are downloaded (ie. the festvox stuff). Then a link is created from Festival to the MBROLA databases in /opt (this is to avoid duplicating MBROLA voices in several places to accomodate each TTS system). Uses also es-es flag to optionnally include Spanish voices. Finally, all examples are also installed (in /usr/lib/festival/examples) so that the (intro) function described in the manual actually works.
Created attachment 55320 [details] Ebuild
Ok, I like some of these changes, but there are problems preventing me from merging in this ebuild. I moved things to /usr/share for a reason... it doesn't belong in /usr/lib. /usr/lib is for binary libraries. It has turned to a dumping ground in recent years for stuff that belongs elsewhere. Examples should go in /usr/share/doc/<pkg>/examples. Non-arch dependent stuff should go in /usr/share/festival. Executables should go in /usr/libexec/festival. I'll be fixing it up, but i thought you should know the reasons for my changes.
in cvs. thanks.
You are perfectly right about installing the examples to /usr/share/doc/... I wrote this ebuild quite a while ago, I do remember though that I had to install the examples in /usr/lib because I wanted to have the (intro) function work and I could not make it with examples in /usr/share/doc. I did not try hard, though, because my main goal was to staighten relationships between Festival and MBROLA. Did you find a fix for that? If not, I can go back to it if you like. I did not know about this libexec directory. What is its purpose? How different is it from /usr/bin?
/usr/bin is for executables that users will run. /usr/libexec is for executables that applications will run (like helper apps)... That's pretty much the one sentence answer ;)
