17 Jul
2009
17 Jul
'09
4:41 p.m.
I've been settling into my own Gentoo system, and so far haven't had any
trouble with unmasked pro-audio packages (for numbered versions anyway)
interfering with anything else in portage. It seems to me that pro-audio is
not very well maintained. I've had to hack several ebuilds to get them to
work, but for the ones that do, likely any masks are just because no one has
tested the ebuild, or because it is live. But more people care about jack
and Ardour so you're likely to find more support on those. Anyway, I would
say don't be afraid of the masked packages. Sometimes the live ebuilds will
work, sometimes not, you may have to fix things yourself and submit bugs
upstream. Though so far my practice has been to build stable versions, then
rebuild with cvs versions as I want. Bad idea to use live ebuilds if you
want something working right away, but if you really want that latest
feature or bug fix, just try it.
I generally haven't built any dbus support, and I'm not sure how jack itself
uses dbus. Not sure about "classic" either, but for those undocumented
flags, I find the best thing to do is just open the ebuild and see what
options those flags are passing to configure (which you should be able to
figure out without any knowledge of how ebuilds work) and then see what
those do.
On Thu, Jul 16, 2009 at 7:11 PM, sonofzev(a)iinet.net.au <
sonofzev(a)iinet.net.au> wrote:
Live ebuilds are always masked for this very reason. However you may find
that
some things are worth unmasking. (I have found that for my hardware I need
to use
the live ebuild for FFADO and Jack to get the best results..
You won't find reported bugs on Gentoo for live ebuilds as they aren't
really
supported but the bug you find may be worth checking for and reporting
upstream
(if you intend to help the particular project)... BTW Ardour 2.x live
ebuild is
relatively stable but not 3.x....
I highly recommend you join the pro-audio overlay mailing list for specific
discussion around this overlay... (We won't bite :)
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
All this will hopefully change in future and was
discussed in some
length on the LAD list some time ago. Until that changes I personally
recommend to compile jack without dbus unless you want to use laditools.
I use Gentoo pro audio overlay, I have found if using FFADO i seem to need
to
have the dbus USE flag turned on.
Also, I'm new to the whole live ebuilds
thing. I see that the
overlay offers Ardour, Jack, and many other things in the form of
direct CVS snapshots. It seems that these are prefered, however, it
looks like they often require unmasked versions of dependency
programs. Should I be afraid of that? For example, the live ebuild
for Ardour seems to be trying to pull in a version of aubio that is
masked for amd64, though I didn't see a bug in the bug database
explaining why. Should I simply unmask any package that is demanded
of a program in the overlay on the basis that overlay programs are
basically bleeding edge anyway?
I can't help you with that specifically since I never used gentoo but
as a general guideline: stay away from it if you don't know what you're
doing. A CVS (or any version control system for that matter) checkout
might be totally broken and there's no guarantee that it will even
compile.