2010/12/22 Dale <rdalek1...@gmail.com>: > Jesús J. Guerrero Botella wrote: >> >> 2010/12/22 Paul Hartman<paul.hartman+gen...@gmail.com>: >> >>> >>> As far as I can remember I think k3bsetup was more related to changing >>> permissions on cdrecord& device nodes, not about detecting devices. >>> >> >> I really can't remember. But there had to be a way to select your >> writer before HAL got into scene. As said, I don't know if that code >> is still there. Much more taking into account that in the middle there >> has been the port to kde4. >> >> > > I noticed the other day that some KDE stuff pulled in policykit. I checked > and noticed this: > > [ebuild U ] app-cdr/k3b-2.0.1-r1 [2.0.0] USE="dvd encode flac mad vorbis > wav (-aqua) -debug -emovix -ffmpeg (-kdeenablefinal) -lame -musepack > -musicbrainz -sndfile -sox -taglib -vcd" LINGUAS="-ast -be -bg -ca > -...@valencia -cs -csb -da -de -el -en_GB -eo -es -et -eu -fi -fr -ga -gl -he > -hi -hne -hr -hu -is -it -ja -km -ko -ku -lt -mai -nb -nds -nl -nn -oc -pa > -pl -pt -pt_BR -ro -ru -se -sk -sl -sv -th -tr -uk -zh_CN -zh_TW" 11,982 kB > > I don't see any mention of hal there. That is the unstable k3b on amd64. > No mention of hal on cdrtools either. Maybe there is light at the end of > the tunnel. ;-)
No. There's no qt use flag for kde apps either. That doesn't mean qt is not required. USE flags are for optional features. HAL is not optional, but mandatory for k3b at this stage. The dependency is in the ebuild if you look inside. -- Jesús Guerrero Botella
