On April 11, 2004 09:37 pm, Curtis Sloan wrote: > On Sat April 10 2004 21:56, nick wrote: > > On April 10, 2004 02:22 pm, Curtis Sloan wrote: > > > I don't use Gentoo, but I do compile the most recent ALSA source > > > releases in addition to the kernel driver (can't get enough bleeding > > > edge ;-) > > > > Which would be a good reason to use gentoo. ;-D > > Touch�. :-) I am not opposed at all to using Gentoo; my two outstanding > reasons for not using are: 1) I only have a PIII 450MHz w/ 256MB RAM and > compiling WINE alone takes two hours, and 2) I can be unsettlingly lazy > sometimes (i.e. untested binary packages are my friends sometimes). ;-D > > Feel free to refute either of these reasons and you may convert me, > especially point 1. ;-)
I wont argue on either point except to point out that [as was said] with emerge you don't even need to be at the machine and compiling is [usually] so easy its a trivial task [it takes care of dependancies on its own, etc. I know RPM dependancies can be a huge headache from personal experience]. Also for the really large [X, KDE, Gnome, OOo etc] packages there are binaries available, and you can even throw the binary in to use, then compile your own later [say while youre sleeping] and emerge will keep everything in order. You can even stop and resume emerge later. Anything you emerge can be put into your own custom binary package for quick use later as well. Its a damn sexy tool. > > <snip> > > > > Does having an ALSA USE flag on Gentoo mean for the kernel, or for > > > compiling ALSA separately? Sorry for not being "hip" and in-the-know > > > about Gentoo. ;-D > > > > Actually it tells emerge [gentoo package manager] to add in ALSA support > > to packages which have it as a compile-time option. That in turn causes > > ALSA to become a necessary dependancy, hence it gets compiled. > > Caveat emptor with me not being a Gentoo expert, but I would expect that > this is where ALSA source releases such as alsa-libs and alsa-oss are being > called upon (to be compiled). Those two packages don't require the > configured Linux kernel source to compile, but they do need to find an > already compiled ALSA driver (and alsa-driver requires compiled kernel > source :-P). So there may be a bit of a 'chicken and the egg' scenario > happening for you. Of course this is strictly conjecture, since I'm > speaking of source tarball compiles, and not emerge packages. emerge uses source tarballs for its 'packages'. > > > When I said I > > injected it that means I told it ALSA was installed, which it was, but in > > a different way. Kinda confusing, esp if another package needs the ALSA > > source to be able to compile. > > Maybe not a bad thing, if you did already have some alsa-lib, alsa-oss and > alsa-utils portage packages installed (compiled? What do Gentooers say, > anyway? ;-) installed/compiled/emerged are generally understood. > previously. If not, that could be where things are going > south. > > I think the sometimes confusing part is that "ALSA" is now included in the > kernel (as of 2.6), but all this refers to is alsa-driver. > > <snip> > > > So I still need alsa-lib, but alsa-driver is in the kernel? > > Yup. Here's the skinny: <snip> Havent had time yet but Im confident I can make it work, thanks. > > HTH, > Curtis > > _______________________________________________ > clug-talk mailing list > [EMAIL PROTECTED] > http://clug.ca/mailman/listinfo/clug-talk_clug.ca _______________________________________________ clug-talk mailing list [EMAIL PROTECTED] http://clug.ca/mailman/listinfo/clug-talk_clug.ca
