gentoo seems to have really messed up the ardour ebuild. to be honest, i am getting a little tired of hearing about gentoo problems.
i’d suggest that you get onto a gentoo forum, and suggest that the gentoo ebuild maintainer for ardour show up on our IRC channel and introduce themselves. we need to talk …
Actually, Paul, that’s kind of in a sort of influx now. That’s probably most of the problem. I’ve found it easiest for me to handle ebuild problems and submit them. I’ve done this for many audio apps in the past.
I thought this might be a config issue or something. If not, I’ll hit the source and start working with it myself.
The ebuild doesn’t make final changes to the /etc directory. They are put in temporary, in Gentoo, until you run etc-update. If you emerge Ardour2 then run it, it will create the wrong ardour.rc in your home directory. Delete the .rc file, run etc-update to get Ardour’s /etc files all correct then rerun Ardour.
Not an ebuild problem. Just a stupid human (me) problem.
I had the same issue. The gentoo ebuild maintainer should be aware that the Ardour /etc stuff is usually not edited manually or with other words MUST be updated on a version update.
The intension of the etc-update after installtion step is obvious: It should avoid that new installations override customized configuration files. In the Ardour case, all files under /etc should be updated with the update process. That would be save i guess