maybe you're already doing this, but thought its worth mentioning.<br><br>if you unmask packages, make sure you set ACCEPT_KEYWORDS="~x<arch>" in /etc/portage/package.keywords<br><br>setting that line in make.conf can be disastrous, as in its easier to reinstall everything. and yes, that sucks as well. I've done it :(<br>
<br>pretty much everything in pro-audio overlay is masked. i believe they have a mailing list as well.<br><br><br><div class="gmail_quote">On Fri, Jul 17, 2009 at 12:01 PM, Brent Busby <span dir="ltr"><<a href="mailto:brent@keycorner.org">brent@keycorner.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">On Fri, 17 Jul 2009, Tim Jones wrote:<br>
<br>
> I've been settling into my own Gentoo system, and so far haven't had<br>
> any trouble with unmasked pro-audio packages (for numbered versions<br>
> anyway) interfering with anything else in portage. It seems to me that<br>
> pro-audio is not very well maintained. I've had to hack several<br>
> ebuilds to get them to work, but for the ones that do, likely any<br>
> masks are just because no one has tested the ebuild, or because it is<br>
> live.<br>
<br>
</div>Since the time I wrote earlier, I've had significant progress getting<br>
things installed, mostly from avoiding the live CVS versions of<br>
everything, and settling for Jack 0.116.2, which is still 0.116 or newer<br>
as cautioned on the Ardour site. (I compiled with no DBus or firewire<br>
support, since I don't use Ffado or FreeBob.) Everything now seems to<br>
coexist well with my other apps and system libraries. I've got Ardour<br>
2.7.1.<br>
<br>
My next challenge is to pick a version of rt-sources and get that<br>
configured and setup. I usually prefer to setup a kernel with modules<br>
that my current system has or is likely to ever have, and put the ones<br>
that are needed to boot into the kernel statically, so I'm going to see<br>
if I can do without an initrd. That certainly out to be possible<br>
though. I just don't like having ninety drivers I don't use autoloaded<br>
by 'discover' during the bootup...it's annoying.<br>
<br>
I wonder if it's better to go with the unmasked rt-sources-2.6.16-r29<br>
(which I see has a very high patchlevel number, so apparently a lot of<br>
time is going into it), or the newest rt-sources-2.6.29.2-r11, which is<br>
more current, but masked. I asked this recently on the Pro-Audio<br>
overlay list, so I'll see what they say there.<br>
<div class="im"><br>
> But more people care about jack and Ardour so you're likely to find<br>
> more support on those. Anyway, I would say don't be afraid of the<br>
> masked packages.<br>
<br>
</div>Yeah, I've seen so many packages in Pro-Audio that needed unmasking to<br>
install that I've just started treating that as par for the course in<br>
the overlay. I'm still sticking with stable packages for my base system<br>
though.<br>
<div class="im"><br>
> I generally haven't built any dbus support, and I'm not sure how jack<br>
> itself uses dbus. Not sure about "classic" either, but for those<br>
> undocumented flags, I find the best thing to do is just open the<br>
> ebuild and see what options those flags are passing to configure<br>
> (which you should be able to figure out without any knowledge of how<br>
> ebuilds work) and then see what those do.<br>
<br>
</div>I did finally find a websvn interface to the changelogs on the overlay<br>
site that described that: It's for if you'd like to compile both Dbus<br>
*and* non-Dbus Jack -- you can enable "dbus" and "classic" together.<br>
I've just gone with 0.116.2 and no Dbus, and that seems to coexist with<br>
everything else nicely.<br>
<div class="im"><br>
--<br>
+ Brent A. Busby + "We've all heard that a million monkeys<br>
+ UNIX Systems Admin + banging on a million typewriters will<br>
+ University of Chicago + eventually reproduce the entire works of<br>
+ Physical Sciences Div. + Shakespeare. Now, thanks to the Internet,<br>
+ James Franck Institute + we know this is not true." -Robert Wilensky<br>
_______________________________________________<br>
</div><div><div></div><div class="h5">Linux-audio-user mailing list<br>
<a href="mailto:Linux-audio-user@lists.linuxaudio.org">Linux-audio-user@lists.linuxaudio.org</a><br>
<a href="http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user" target="_blank">http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user</a><br>
</div></div></blockquote></div><br>