Gentoo Archives: gentoo-user

From: "Jesús J. Guerrero Botella" <jesus.guerrero.botella@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Persistent hal
Date: Wed, 22 Dec 2010 17:04:00
Message-Id: AANLkTino_sD0+X7PrVLvGNsvqiWjJavJF6mLms7WCavz@mail.gmail.com
In Reply to: Re: [gentoo-user] Persistent hal by Dale
1 2010/12/22 Dale <rdalek1967@×××××.com>:
2 > Jesús J. Guerrero Botella wrote:
3 >>
4 >> 2010/12/22 Paul Hartman<paul.hartman+gentoo@×××××.com>:
5 >>
6 >>>
7 >>> As far as I can remember I think k3bsetup was more related to changing
8 >>> permissions on cdrecord&  device nodes, not about detecting devices.
9 >>>
10 >>
11 >> I really can't remember. But there had to be a way to select your
12 >> writer before HAL got into scene. As said, I don't know if that code
13 >> is still there. Much more taking into account that in the middle there
14 >> has been the port to kde4.
15 >>
16 >>
17 >
18 > I noticed the other day that some KDE stuff pulled in policykit.  I checked
19 > and noticed this:
20 >
21 > [ebuild     U ] app-cdr/k3b-2.0.1-r1 [2.0.0] USE="dvd encode flac mad vorbis
22 > wav (-aqua) -debug -emovix -ffmpeg (-kdeenablefinal) -lame -musepack
23 > -musicbrainz -sndfile -sox -taglib -vcd" LINGUAS="-ast -be -bg -ca
24 > -ca@valencia -cs -csb -da -de -el -en_GB -eo -es -et -eu -fi -fr -ga -gl -he
25 > -hi -hne -hr -hu -is -it -ja -km -ko -ku -lt -mai -nb -nds -nl -nn -oc -pa
26 > -pl -pt -pt_BR -ro -ru -se -sk -sl -sv -th -tr -uk -zh_CN -zh_TW" 11,982 kB
27 >
28 > I don't see any mention of hal there.  That is the unstable k3b on amd64.
29 >  No mention of hal on cdrtools either.  Maybe there is light at the end of
30 > the tunnel.  ;-)
31
32 No. There's no qt use flag for kde apps either. That doesn't mean qt
33 is not required.
34
35 USE flags are for optional features. HAL is not optional, but
36 mandatory for k3b at this stage. The dependency is in the ebuild if
37 you look inside.
38
39
40 --
41 Jesús Guerrero Botella

Replies

Subject Author
Re: [gentoo-user] Persistent hal Dale <rdalek1967@×××××.com>