Hi! I use SuSE 9.1 (kde 3.2.1) and want to compile kde 3.4.1. I have compiled kde 3.1, 3.2, 3.3, and 3.4 in the past on other distros, so I am not completely new to this procedure. I noticed tha SuSE installs kde in /opt/kde3, but has overriding icons and config files in /etc/opt/kde3. For example, /opt/kde3/share/icons/crystalsvg/128x128/apps has a kmenu.png icon, the kde default, and /etc/opt/kde3/share/icons/crystalsvg/128x128/apps has a kmenu.png, which is a lizard head, and is the kmenu icon. If I delete the lizard head, the icon goes back to the /opt/kde3/.../kmenu.png. I have seen the variable $KDEDIRS pop up in the past, but it isn't set in this case for me. How could I tell the kde I am going to compile to install in /opt/kde3, and look in but not write to /etc/opt/kde3 like SuSE has it? Do I need a patch for kde? Thanks! -Steven
Steven Pasternak wrote:
Hi! I use SuSE 9.1 (kde 3.2.1) and want to compile kde 3.4.1. I would just suggest upgrading using the SuSE compiled binaries, such as at http://ftp.gwdg.de/pub/linux/suse/ftp.suse.com/suse/i386/supplementary/KDE/u... which are for 3.4.1. You could even add the yast-source and upgrade using Yast. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
Joe Morris (NTM) wrote:
Steven Pasternak wrote:
Hi! I use SuSE 9.1 (kde 3.2.1) and want to compile kde 3.4.1.
I would just suggest upgrading using the SuSE compiled binaries, such as at http://ftp.gwdg.de/pub/linux/suse/ftp.suse.com/suse/i386/supplementary/KDE/u...
which are for 3.4.1. You could even add the yast-source and upgrade using Yast. Some of us never enjoyed mama spoon feeding us as kids and feel the same way about Mama SuSE/Mandriva/RedHat etc. Linux is great and we can play with whatever takes our fancy to our heart's content or coronary - even with SuSE .... TINAF (This Is Not A Flame), just a statement. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot Retired IBM Mainframes and Sun Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks
Steven Pasternak wrote:
Hi! I use SuSE 9.1 (kde 3.2.1) and want to compile kde 3.4.1. I have compiled kde 3.1, 3.2, 3.3, and 3.4 in the past on other distros, so I am not completely new to this procedure. I noticed tha SuSE installs kde in /opt/kde3, but has overriding icons and config files in /etc/opt/kde3. For example, /opt/kde3/share/icons/crystalsvg/128x128/apps has a kmenu.png icon, the kde default, and /etc/opt/kde3/share/icons/crystalsvg/128x128/apps has a kmenu.png, which is a lizard head, and is the kmenu icon. If I delete the lizard head, the icon goes back to the /opt/kde3/.../kmenu.png. I have seen the variable $KDEDIRS pop up in the past, but it isn't set in this case for me. How could I tell the kde I am going to compile to install in /opt/kde3, and look in but not write to /etc/opt/kde3 like SuSE has it? Do I need a patch for kde? Thanks! -Steven
This must be the result of a configure option. I've been looking for a while for a rpm option to display the configure options used to build a package - thought I'd come across it somewhere before, but I may be mistaken, it may have been something like gcc or binutils. The only suggestions I can come up with is to use alien to generate a .tgz file from the source and have a look at the Makefiles and config.log. rpmbuild --rebuild a SuSE KDE source rpm and tee to a file and also check in /usr/src/packages/BUILD. I'd like to know the answer myself as when you build a package, it tends to put the stuff in /opt/kde3 rather than /etc/opt/kde3. Third suggestion, perhaps you could find out who builds the SuSE kde packages and get an answer straight from the horse's mouth. It's many years since I've built KDE from the ground up mainly because of other stuff I spend my time doing, GOOD LUCK! and have fun. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot Retired IBM Mainframes and Sun Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks
On Fri, 2005-06-17 at 10:43 +0100, Sid Boyce wrote:
This must be the result of a configure option. I've been looking for a while for a rpm option to display the configure options used to build a package - thought I'd come across it somewhere before, but I may be mistaken, it may have been something like gcc or binutils. The only suggestions I can come up with is to use alien to generate a .tgz file from the source and have a look at the Makefiles and config.log. rpmbuild --rebuild a SuSE KDE source rpm and tee to a file and also check in /usr/src/packages/BUILD. I'd like to know the answer myself as when you build a package, it tends to put the stuff in /opt/kde3 rather than /etc/opt/kde3. Third suggestion, perhaps you could find out who builds the SuSE kde packages and get an answer straight from the horse's mouth. It's many years since I've built KDE from the ground up mainly because of other stuff I spend my time doing, GOOD LUCK! and have fun.
Wouldn't the options be contained in the spec file from the src rpm? -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
Ken Schneider wrote:
On Fri, 2005-06-17 at 10:43 +0100, Sid Boyce wrote:
This must be the result of a configure option. I've been looking for a while for a rpm option to display the configure options used to build a package - thought I'd come across it somewhere before, but I may be mistaken, it may have been something like gcc or binutils. The only suggestions I can come up with is to use alien to generate a .tgz file from the source and have a look at the Makefiles and config.log. rpmbuild --rebuild a SuSE KDE source rpm and tee to a file and also check in /usr/src/packages/BUILD. I'd like to know the answer myself as when you build a package, it tends to put the stuff in /opt/kde3 rather than /etc/opt/kde3. Third suggestion, perhaps you could find out who builds the SuSE kde packages and get an answer straight from the horse's mouth. It's many years since I've built KDE from the ground up mainly because of other stuff I spend my time doing, GOOD LUCK! and have fun.
Wouldn't the options be contained in the spec file from the src rpm?
Yes, you can get a source RPM, "alien -t xxx.src.rpm" which will break out the spec file separately or have it included in the xxx.tgz file. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot Retired IBM Mainframes and Sun Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks
Ken Schneider wrote:
Wouldn't the options be contained in the spec file from the src rpm?
Yes, you can get a source RPM, "alien -t xxx.src.rpm" which will break out the spec file separately or have it included in the xxx.tgz file. Or do it the easy way, and use mc and copy the spec file (or just view it if that is all that's needed). BTW, I think you will find most of
Sid Boyce wrote: the options you seek in /etc/opt/kde3/common_options. Since SuSE has been traditionally a KDE based distro, and their integration of KDE is one of their strong points, even though I have rebuilt and tweaked some src.rpms, I wonder why someone would want to have a SuSE distro and build such fundamental softwares from source as KDE instead of using the supplied supplementary binaries already built by SuSE. Linux IS all about choice though, so to each their own. ;-) Can't believe it would help the rpm database situation at all either, but I guess we each choose our own challenges. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
Joe Morris (NTM) wrote:
Sid Boyce wrote:
Ken Schneider wrote:
Wouldn't the options be contained in the spec file from the src rpm?
Yes, you can get a source RPM, "alien -t xxx.src.rpm" which will break out the spec file separately or have it included in the xxx.tgz file.
Or do it the easy way, and use mc and copy the spec file (or just view it if that is all that's needed). BTW, I think you will find most of the options you seek in /etc/opt/kde3/common_options.
Since SuSE has been traditionally a KDE based distro, and their integration of KDE is one of their strong points, even though I have rebuilt and tweaked some src.rpms, I wonder why someone would want to have a SuSE distro and build such fundamental softwares from source as KDE instead of using the supplied supplementary binaries already built by SuSE. Linux IS all about choice though, so to each their own. ;-) Can't believe it would help the rpm database situation at all either, but I guess we each choose our own challenges.
I looked at /etc/opt/kde3/common_otions and only saw --sysconfdir=/etc, no references to $SYSCONFDIR/opt/kde3, so I discounted it. If the existing RPM's are replaced by an update, there should be no problems. I saw problems in may be 8.x and ended up cp'ing stuff between /opt/kde3 and /etc/opt/kde3 to get new stuff seen in the menu. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot Retired IBM Mainframes and Sun Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks
participants (4)
-
Joe Morris (NTM) -
Ken Schneider -
Sid Boyce -
Steven Pasternak