i installed xcdroast in 8.2 and my impression was that yast would handle dependencies but when i run xcdroast it tells me i am missin cdrecord ** WARNING **: Installation problem? /usr/X11R6/bin/cdrecord not found. ** WARNING **: Installation problem? /usr/X11R6/bin/mkisofs not found. ** WARNING **: Installation problem? /usr/X11R6/bin/readcd not found. ** WARNING **: Installation problem? /usr/X11R6/bin/cdda2wav not found. was yast suppose to handle that?
The 03.05.07 at 04:44, R R wrote:
i installed xcdroast in 8.2 and my impression was that yast would handle dependencies but when i run xcdroast it tells me i am missin cdrecord
** WARNING **: Installation problem? /usr/X11R6/bin/cdrecord not found.
That problem has been around for a long time. xcdroast looks for cdrecord in that directory, but Suse puts it in /usr/bin/cdrecord, and then creates some symlinks. Check if xcdroast works, and if not, create the symlinks yourself. I can not check, I use 8.1 and my own compiled version. -- Cheers, Carlos Robinson
"Carlos E. R."
dependencies but when i run xcdroast it tells me i am missin cdrecord
** WARNING **: Installation problem? /usr/X11R6/bin/cdrecord not found.
This is a clear sign of the maintainer (moi) goofing :) When working on problems in biarch systems (mixed 32/64 Bits like AMD64) I accidently removed the program copies.
Check if xcdroast works, and if not, create the symlinks yourself.
The symlinks have a drawback in that xcdrosts usermode doesn't work. That's why the update package has *copies* of the respective binaries in that place. Philipp
On Thu, 2003-05-08 at 01:03, Philipp Thomas wrote:
The symlinks have a drawback in that xcdrosts usermode doesn't work. That's why the update package has *copies* of the respective binaries in that place.
Wouldn't it make about 100% more sense to change the source so xcdroast works directly on the binaries in /usr/bin ? What could possibly be the rationale for working on symlinks or - even worse - full copies?
Anders Johansson
Wouldn't it make about 100% more sense to change the source so xcdroast works directly on the binaries in /usr/bin ? What could possibly be the rationale for working on symlinks or - even worse - full copies?
xcdroast makes these binaries setuid to special owner/group to make it possible for a normal user to burn CDs. You wouldn't want this to happen to the normal binaries. But agreed, this could need some changes. Philipp
On Thursday 08 May 2003 09:20, Philipp Thomas wrote:
xcdroast makes these binaries setuid to special owner/group to make it possible for a normal user to burn CDs. You wouldn't want this to happen to the normal binaries.
Why not? If root wants to set things up using the xcdroast ownership method, why should there be binaries in /usr/bin using a different setup?
The 03.05.08 at 01:03, Philipp Thomas wrote:
The symlinks have a drawback in that xcdrosts usermode doesn't work. That's why the update package has *copies* of the respective binaries in that place.
True, I forgot that: I modified those binaries myself. I didn't think of using copies... what about hardlinks instead? -- Cheers, Carlos Robinson
participants (4)
-
Anders Johansson -
Carlos E. R. -
Philipp Thomas -
R R