[gentoo-user] Persistent hal
I don't really want it, but my system still has hal installed. According to equery depends, it seems that there are still two packages that unconditionally depend on hal (besides hal-info): k3b and gnome-mount. I don't care much about gnome-mount (this is primarily a KDE system), but I definitely use K3B a lot. I don't see any use flags to change with respect to k3b, so I'm feeling I''m missing something. Help? ++ kevin
Re: [gentoo-user] Persistent hal
On Wed, Dec 22, 2010 at 7:26 AM, Kevin O'Gorman kogor...@gmail.com wrote: I don't really want it, but my system still has hal installed. According to equery depends, it seems that there are still two packages that unconditionally depend on hal (besides hal-info): k3b and gnome-mount. I don't care much about gnome-mount (this is primarily a KDE system), but I definitely use K3B a lot. I don't see any use flags to change with respect to k3b, so I'm feeling I''m missing something. Help? ++ kevin You are not as far as I can tell. I was looking at that yesterday. Saw the same thing. - Mark
Re: [gentoo-user] Persistent hal
On Wed, Dec 22, 2010 at 7:33 AM, Mark Knecht markkne...@gmail.com wrote: On Wed, Dec 22, 2010 at 7:26 AM, Kevin O'Gorman kogor...@gmail.com wrote: I don't really want it, but my system still has hal installed. According to equery depends, it seems that there are still two packages that unconditionally depend on hal (besides hal-info): k3b and gnome-mount. I don't care much about gnome-mount (this is primarily a KDE system), but I definitely use K3B a lot. I don't see any use flags to change with respect to k3b, so I'm feeling I''m missing something. Help? You are not as far as I can tell. I was looking at that yesterday. Saw the same thing. That's pretty strange. I loked further, and found that --depclean wanted to ditch the gnome-mounter, which I promptly unmerged myself, so K3B is the only thing left that wants hal. Of course, I'm sticking with x86 stable, which means hal-2.0.0. Maybe the ~x86 version in there fixes this? -- Kevin O'Gorman, PhD
Re: [gentoo-user] Persistent hal
~amd64 (which is k3b-2.0.1-r1) still depends on HAL. The last time I checked this, work was on-going to solve that. But, as of now, HAL is the only way k3b has to find devices, in gentoo at least. I remember that in the past there was a configurator where you could manually configure the devices from k3b. I don't know if that code is still there. Maybe the it is and the problem is that Gentoo removes it. The message at the end of the ebuild is suspicious in this regard. echo elog We don't install k3bsetup anymore because Gentoo doesn't need it. elog If you get warnings on start-up, uncheck the \Check system elog configuration\ option in the \Misc\ settings window. echo It might be possible to disable hal via some flag and then remove the -DK3B_BUILD_K3BSETUP=OFF above you be able to manually configure k3b without needing HAL. -- Jesús Guerrero Botella
Re: [gentoo-user] Persistent hal
2010/12/22 Jesús J. Guerrero Botella jesus.guerrero.bote...@gmail.com: ~amd64 (which is k3b-2.0.1-r1) still depends on HAL. The last time I checked this, work was on-going to solve that. But, as of now, HAL is the only way k3b has to find devices, in gentoo at least. I remember that in the past there was a configurator where you could manually configure the devices from k3b. I don't know if that code is still there. Maybe the it is and the problem is that Gentoo removes it. The message at the end of the ebuild is suspicious in this regard. echo elog We don't install k3bsetup anymore because Gentoo doesn't need it. elog If you get warnings on start-up, uncheck the \Check system elog configuration\ option in the \Misc\ settings window. echo It might be possible to disable hal via some flag and then remove the -DK3B_BUILD_K3BSETUP=OFF above you be able to manually configure k3b without needing HAL. As far as I can remember I think k3bsetup was more related to changing permissions on cdrecord device nodes, not about detecting devices.
Re: [gentoo-user] Persistent hal
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. -- Jesús Guerrero Botella
Re: [gentoo-user] Persistent hal
Jesús J. Guerrero Botella wrote: 2010/12/22 Paul Hartmanpaul.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. ;-) Dale :-) :-)
Re: [gentoo-user] Persistent hal
2010/12/22 Dale rdalek1...@gmail.com: Jesús J. Guerrero Botella wrote: 2010/12/22 Paul Hartmanpaul.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
Re: [gentoo-user] Persistent hal
Am 22.12.2010 17:51, schrieb Dale: I noticed the other day that some KDE stuff pulled in policykit. I checked and noticed this: 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. ;-) Shao ~ # emerge k3b -vp These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N] sys-apps/hal-0.5.14-r4 USE=X acpi crypt -apm -debug -dell -disk-partition -doc -laptop (-selinux) 0 kB [0] [ebuild U ] app-cdr/k3b- [2.0.1-r1] USE=dvd encode ffmpeg flac lame mad musepack musicbrainz taglib vorbis wav (-aqua) -debug -emovix (-kdeenablefinal) -sndfile -sox -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%) 0 kB [0=1] Total: 2 packages (1 upgrade, 1 new), Size of downloads: 0 kB Portage tree and overlays: [0] /usr/portage [1] /var/lib/layman/kde So even the live build still needs hal.. But now that KDE 4.6 comes without a need for hal I am sure that k3b will drop that dependency soon. Greetings Sebastian Beßler
Re: [gentoo-user] Persistent hal
Jesús J. Guerrero Botella wrote: 2010/12/22 Dalerdalek1...@gmail.com: Jesús J. Guerrero Botella wrote: 2010/12/22 Paul Hartmanpaul.hartman+gen...@gmail.com: As far as I can remember I think k3bsetup was more related to changing permissions on cdrecorddevice 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. Oh yea. I was hoping anyway. Maybe soon. Dale :-) :-)
