Re: [newbie] src.rpm headaches.
On Saturday 19 March 2005 3:50 pm, Tom wrote: Now, James, when you installed the system did you select Development ? Without those additions to your system you probly can't compile anything. Other questions: are you just doin all this as an exercise? an why don't you just use Mandrakes' pre-compiled packages for kdeutils? IOW's, what are you tryin to accomplish? Hello, I have the Mandrake 6-disc set, so I have these binaries, and don't need to compile anything. Having just successfully 'hatched' kdeutils...src.rpm (I downloaded a new one), with rpmbuild [thanks to all of you, and I certainly didn't intend to set off any controversy. I'll have to read these man pages) Inasmuch as I doesn't really have a prayer of understanding C++, or the maze of linked header files, etc. (most of my programing knowledge in Linux and C comes from Learning C in 28 days) this was all an exercise. Its genesis comes from my fondness of Kedit. It seems like a really simple program, and I thought that it might be possible to change the behavior of its Tab key (i.e., how many spaces are printed when tab is presses. So far in this exercise, I've discovered .kcfg files (hence Kcfgcreator, hence unsermake) and now rpmbuild, and kconfig_compiler, kconfigskeleton.h and kconfig.h (and I still haven't found anything that says main). As expected, I'm not really more enlightened as concerns my original goal, but I'm having fun. If you have any suggestions about books to teach the neophyte about program development (I know no 'object oriented' stuff, and am shaky on all the libs etc.) Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] src.rpm headaches.
James Henry Maiewski wrote: On Saturday 19 March 2005 3:50 pm, Tom wrote: Now, James, when you installed the system did you select Development ? Without those additions to your system you probly can't compile anything. Other questions: are you just doin all this as an exercise? an why don't you just use Mandrakes' pre-compiled packages for kdeutils? IOW's, what are you tryin to accomplish? Hello, I have the Mandrake 6-disc set, so I have these binaries, and don't need to compile anything. Having just successfully 'hatched' kdeutils...src.rpm (I downloaded a new one), with rpmbuild [thanks to all of you, and I certainly didn't intend to set off any controversy. I'll have to read these man pages) Don't pay any attention to us jawin at each other. There wasn't really any controversy, just back'n forth exploration. I came out of it aware of a pending change I had no idea about. An usually I'm the one always warning of comming changes ;) Inasmuch as I doesn't really have a prayer of understanding C++, or the maze of linked header files, etc. (most of my programing knowledge in Linux and C comes from Learning C in 28 days) this was all an exercise. Its genesis comes from my fondness of Kedit. It seems like a really simple program, and I thought that it might be possible to change the behavior of its Tab key (i.e., how many spaces are printed when tab is presses. So far in this exercise, I've discovered .kcfg files (hence Kcfgcreator, hence unsermake) and now rpmbuild, and kconfig_compiler, kconfigskeleton.h and kconfig.h (and I still haven't found anything that says main). As expected, I'm not really more enlightened as concerns my original goal, but I'm having fun. As an exercise, learning is the best reason. You should also acquaint yourself with compiling a kernel from kernel-source. One day you might even need to. If you have any suggestions about books to teach the neophyte about program development (I know no 'object oriented' stuff, and am shaky on all the libs etc.) More than 15 years ago, with no prior knowledge, I walked into a scientific book store. They had one whole wall devoted to programming languages. I saw that most of the shelf space was devoted to C/C++. I found a large paperback book that also came with CD's for installin a compiler, Turbo C++ (sorry I don't remember the name). So I bought it an started teaching myself C++. It was all pretty straightforward ... at least until I got into hierarchies, classes, public and private, and so on. Well worth the effort, and quite enjoyable. The only 'connection' I had then was to dial into BBS's. Found quite a bit of resources for programming there, even local user groups I began to attend. Anyhow, I believe you can find comprehensive tutorials for just about any programming language online these days. Along with plenty source examples. No real need to buy a book, and you've already got a C/C++ compiler (other compilers are also available). I'll leave it to others with more recent experience to recommend current languages and such. I've all but forgotten everything I use to know about C++. Still, it was a priceless experience, and greatly enhanched my computer, troubleshootin skills. Go for it James -- Tom Brinkman Corpus Christi, Texas Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] src.rpm headaches.
James Henry Maiewski wrote: On Saturday 19 March 2005 3:50 pm, Tom wrote: Now, James, when you installed the system did you select Development ? Without those additions to your system you probly can't compile anything. Other questions: are you just doin all this as an exercise? an why don't you just use Mandrakes' pre-compiled packages for kdeutils? IOW's, what are you tryin to accomplish? Hello, I have the Mandrake 6-disc set, so I have these binaries, and don't need to compile anything. Having just successfully 'hatched' kdeutils...src.rpm (I downloaded a new one), with rpmbuild [thanks to all of you, and I certainly didn't intend to set off any controversy. I'll have to read these man pages) Inasmuch as I doesn't really have a prayer of understanding C++, or the maze of linked header files, etc. (most of my programing knowledge in Linux and C comes from Learning C in 28 days) this was all an exercise. Its genesis comes from my fondness of Kedit. It seems like a really simple program, and I thought that it might be possible to change the behavior of its Tab key (i.e., how many spaces are printed when tab is presses. So far in this exercise, I've discovered .kcfg files (hence Kcfgcreator, hence unsermake) and now rpmbuild, and kconfig_compiler, kconfigskeleton.h and kconfig.h (and I still haven't found anything that says main). As expected, I'm not really more enlightened as concerns my original goal, but I'm having fun. If you have any suggestions about books to teach the neophyte about program development (I know no 'object oriented' stuff, and am shaky on all the libs etc.) You may want to start with something other then part of the KDE family. While Kate may be a simple program, I don't think building anything that is part of the KDE desktop is simple. This is because of the high level of intergration between the different parts. On the other hand, it definitly will be a learning experence. Mikkel -- Do not meddle in the affairs of dragons, for you are crunchy and taste good with Ketchup! Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
[newbie] src.rpm headaches.
Hello, I downloaded kdeutils-3.2.3-28.3.101mdk.src.rpm to see what I could see, but when I try to install it, it says everything already installed. If these are supposed to go in /usr(/local)/src they are empty. How is the installation of .src.rpm files supposed to work? With an advance of thanks, James Henry Maiewski Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] src.rpm headaches.
On Saturday 19 March 2005 09:01 am, James Henry Maiewski wrote: Hello, I downloaded kdeutils-3.2.3-28.3.101mdk.src.rpm to see what I could see, but when I try to install it, it says everything already installed. If these are supposed to go in /usr(/local)/src they are empty. How is the installation of .src.rpm files supposed to work? The sources unpack to ~/RPM/SOURCES and the spec to ~/RPM/SPECS if you install as user, and to /usr/src/RPM/SOURCES and /usr/src/RPM/SPECS respectively if you install as root. -- /g Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] src.rpm headaches.
James Henry Maiewski wrote:
Hello,
I downloaded kdeutils-3.2.3-28.3.101mdk.src.rpm to see what I could
see, but when I try to install it, it says everything already
installed. If these are supposed to go in /usr(/local)/src they are
empty. How is the installation of .src.rpm files supposed to work?
With an advance of thanks,
James Henry Maiewski
src.rpm's are not to be installed (tho they can be). You can
compile the rpms contained in the src.rpm by doin (as root)
'rpm --rebuild kdeutils-3.2.3-28.3.101mdk.src.rpm'
the resulting rpms will then be found in
/usr/src/RPM/RPMS/i586/
Another example;
'rpm --rebuild --target athlon kdeutils-3.2.3-28.3.101mdk.src.rpm'
will compile the rpms, athlon optimized, and place them in
/usr/src/RPM/RPMS/athlon/
The src.rpm will build _all_ the rpms contained in the
src.rpm. So if you only want to upgrade only kdeutils rpms you
already have installed, cd to one of the above directories and use
'rpm -Fvh *.rpm' ('F' being the important bit)
(this assumes you only have kdeutils* rpms in the dir)
If dependencies are needed, rpm -Fvh, will stop without
installing an display a list of what's needed.
--
Tom Brinkman Corpus Christi, Texas
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com
Re: [newbie] src.rpm headaches.
On Saturday 19 March 2005 10:05 am, Tom wrote: James Henry Maiewski wrote: Hello, I downloaded kdeutils-3.2.3-28.3.101mdk.src.rpm to see what I could see, but when I try to install it, it says everything already installed. If these are supposed to go in /usr(/local)/src they are empty. How is the installation of .src.rpm files supposed to work? With an advance of thanks, James Henry Maiewski src.rpm's are not to be installed (tho they can be). You can compile the rpms contained in the src.rpm by doin (as root) 'rpm --rebuild kdeutils-3.2.3-28.3.101mdk.src.rpm' Not to be too picky, but technically, rpm is deprecated and rpmbuild --rebuild is preferred because it has been split into separate packages. the resulting rpms will then be found in /usr/src/RPM/RPMS/i586/ Just as a general rule it is not a good idea to compile src.rpms as root, because if the buildroot variable is not set, the package will actually get installed on your machine, so as a habit, it is safer to setup the RPM dir in ~/ and build as user. Mandrake is very good about this, but occasionally you get a 3rd party packager that forgets to set this and It's just a good habit. and you can bork the system. Another example; 'rpm --rebuild --target athlon kdeutils-3.2.3-28.3.101mdk.src.rpm' will compile the rpms, athlon optimized, and place them in /usr/src/RPM/RPMS/athlon/ This is cool, and might be fun to experiment to see if this has any effect on your system. The src.rpm will build _all_ the rpms contained in the src.rpm. So if you only want to upgrade only kdeutils rpms you already have installed, cd to one of the above directories and use Just one small point about your use of terminology in order to clarify, you are compiling the source and building the rpm packages as they are specified in the src.rpm's spec file, not releasing already built things packaged together. It kind of sounds like they are being hatched instead of built the way you described it :) -- /g Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] src.rpm headaches.
Greg Meyer wrote: On Saturday 19 March 2005 10:05 am, Tom wrote: James Henry Maiewski wrote: Hello, I downloaded kdeutils-3.2.3-28.3.101mdk.src.rpm to see what I could see, but when I try to install it, it says everything already installed. If these are supposed to go in /usr(/local)/src they are empty. How is the installation of .src.rpm files supposed to work? With an advance of thanks, James Henry Maiewski src.rpm's are not to be installed (tho they can be). You can compile the rpms contained in the src.rpm by doin (as root) 'rpm --rebuild kdeutils-3.2.3-28.3.101mdk.src.rpm' Not to be too picky, but technically, rpm is deprecated and rpmbuild --rebuild is preferred because it has been split into separate packages. hmmm... tell me more. # rpm --rebuild mplayer-fonts-1.0-10mdk.src.rpm ... snip ... Wrote: /usr/src/RPM/RPMS/noarch/mplayer-fonts-1.0-10mdk.noarch.rpm Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.1910 + umask 022 + cd /usr/src/RPM/BUILD + cd mplayer-fonts-1.0 + rm -rf /var/tmp/mplayer-fonts-buildroot + exit 0 Executing(--clean): /bin/sh -e /var/tmp/rpm-tmp.1910 + umask 022 + cd /usr/src/RPM/BUILD + rm -rf mplayer-fonts-1.0 + exit 0 # rpm -Uvh /usr/src/RPM/RPMS/noarch/mplayer-fonts-1.0-10mdk.noarch.rpm Preparing... ### [100%] 1:mplayer-fonts ### [100%] Are you sugesting I should'a used 'rpmbuild --rebuild mplaTab' ? FWIW, the system is as current as can be (cooker 10.2) 2.6.11-2mdkK74 preempt K7 gcc-3.4 (rpm-build-4.2.3-9mdk) the resulting rpms will then be found in /usr/src/RPM/RPMS/i586/ Just as a general rule it is not a good idea to compile src.rpms as root, because if the buildroot variable is not set, the package will actually get installed on your machine, so as a habit, it is safer to setup the RPM dir in ~/ and build as user. Mandrake is very good about this, but occasionally you get a 3rd party packager that forgets to set this and It's just a good habit. and you can bork the system. Two schools, an I'm in the other one ;) 'Sides the OP did cite a Mandrake rpm. More important to me would be direct newbies to always use Mandrake rpms, src.rpms included, to procure wanted apps or dependencies. More over to disdain corrupting their systems with anything 3rd party (includin drivers an apps, rpms or tarballs). Build as user all you want, but if you install closed source binary only taints on it, the precaution to only build rpms (or tarballs for that matter) as user is sort'a moot, borderin on ridiculous. Another example; 'rpm --rebuild --target athlon kdeutils-3.2.3-28.3.101mdk.src.rpm' will compile the rpms, athlon optimized, and place them in /usr/src/RPM/RPMS/athlon/ This is cool, and might be fun to experiment to see if this has any effect on your system. IME, no. But when I ocaisionally do build from source, I include athlon opts just for grins. Mostly kernels (as in 2.6.11-2mdkK74, compiled for athlon, preempt, 4gig ram support). I used Mdk's kernel-source rpm an changed the .config, mostly to gain preempt and support for 1gig of ram. An then only 'cause such a kernel wasn't avaible from Mandrake, pre-compiled. The src.rpm will build _all_ the rpms contained in the src.rpm. So if you only want to upgrade only kdeutils rpms you already have installed, cd to one of the above directories and use Just one small point about your use of terminology in order to clarify, you are compiling the source and building the rpm packages as they are specified in the src.rpm's spec file, not releasing already built things packaged together. It kind of sounds like they are being hatched instead of built the way you described it :) 'hatched'? not sure what you mean Greg. The 'F' switch in 'rpm -Fvh' will only upgrade existing packages on the system, not all packages included in the src.rpm. Good example would be 'xorg' which would create more than a dozen packages, but only about 7 of which are used on my system. -- Tom Brinkman Corpus Christi, Texas Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] src.rpm headaches.
Tom wrote: Greg Meyer wrote: On Saturday 19 March 2005 10:05 am, Tom wrote: James Henry Maiewski wrote: Hello, I downloaded kdeutils-3.2.3-28.3.101mdk.src.rpm to see what I could see, but when I try to install it, it says everything already installed. If these are supposed to go in /usr(/local)/src they are empty. How is the installation of .src.rpm files supposed to work? With an advance of thanks, James Henry Maiewski src.rpm's are not to be installed (tho they can be). You can compile the rpms contained in the src.rpm by doin (as root) 'rpm --rebuild kdeutils-3.2.3-28.3.101mdk.src.rpm' Not to be too picky, but technically, rpm is deprecated and rpmbuild --rebuild is preferred because it has been split into separate packages. hmmm... tell me more. # rpm --rebuild mplayer-fonts-1.0-10mdk.src.rpm ... snip ... Wrote: /usr/src/RPM/RPMS/noarch/mplayer-fonts-1.0-10mdk.noarch.rpm Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.1910 + umask 022 + cd /usr/src/RPM/BUILD + cd mplayer-fonts-1.0 + rm -rf /var/tmp/mplayer-fonts-buildroot + exit 0 Executing(--clean): /bin/sh -e /var/tmp/rpm-tmp.1910 + umask 022 + cd /usr/src/RPM/BUILD + rm -rf mplayer-fonts-1.0 + exit 0 # rpm -Uvh /usr/src/RPM/RPMS/noarch/mplayer-fonts-1.0-10mdk.noarch.rpm Preparing... ### [100%] 1:mplayer-fonts ### [100%] Are you sugesting I should'a used 'rpmbuild --rebuild mplaTab' ? FWIW, the system is as current as can be (cooker 10.2) 2.6.11-2mdkK74 preempt K7 gcc-3.4 (rpm-build-4.2.3-9mdk) From the rpm man page: LEGACY ISSUES Executing rpmbuild The build modes of rpm are now resident in the /usr/bin/rpmbuild executable. Although legacy compatibility provided by the popt aliases below has been adequate, the compatibility is not perfect; hence build mode compatibility through popt aliases is being removed from rpm. Install the rpmbuild package, and see rpmbuild(8) for documentation of all the rpm build modes previously documented here in rpm(8). Add the following lines to /etc/popt if you wish to continue invoking rpmbuild from the rpm command line: It then goes into a table that you can read for your self if you are interested. Mikkel -- Do not meddle in the affairs of dragons, for you are crunchy and taste good with Ketchup! Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] src.rpm headaches.
Mikkel L. Ellertson wrote: Tom wrote: hmmm... tell me more. # rpm --rebuild mplayer-fonts-1.0-10mdk.src.rpm ... snip ... Wrote: /usr/src/RPM/RPMS/noarch/mplayer-fonts-1.0-10mdk.noarch.rpm Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.1910 + umask 022 + cd /usr/src/RPM/BUILD + cd mplayer-fonts-1.0 + rm -rf /var/tmp/mplayer-fonts-buildroot + exit 0 Executing(--clean): /bin/sh -e /var/tmp/rpm-tmp.1910 + umask 022 + cd /usr/src/RPM/BUILD + rm -rf mplayer-fonts-1.0 + exit 0 # rpm -Uvh /usr/src/RPM/RPMS/noarch/mplayer-fonts-1.0-10mdk.noarch.rpm Preparing... ### [100%] 1:mplayer-fonts ### [100%] Are you sugesting I should'a used 'rpmbuild --rebuild mplaTab' ? FWIW, the system is as current as can be (cooker 10.2) 2.6.11-2mdkK74 preempt K7 gcc-3.4 (rpm-build-4.2.3-9mdk) From the rpm man page: LEGACY ISSUES Executing rpmbuild The build modes of rpm are now resident in the /usr/bin/rpmbuild executable. Although legacy compatibility provided by the popt aliases below has been adequate, the compatibility is not perfect; hence build mode compatibility through popt aliases is being removed from rpm. Install the rpmbuild package, and see rpmbuild(8) for documentation of all the rpm build modes previously documented here in rpm(8). Add the following lines to /etc/popt if you wish to continue invoking rpmbuild from the rpm command line: It then goes into a table that you can read for your self if you are interested. Mikkel # less /etc/popt /etc/popt: No such file or directory Do I need to create this file? an why? rpm -rebuild is still very much functional, even on 10.2 Yes, I read the man page. -- Tom Brinkman Corpus Christi, Texas Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] src.rpm headaches.
Tom wrote: Mikkel L. Ellertson wrote: Tom wrote: hmmm... tell me more. # rpm --rebuild mplayer-fonts-1.0-10mdk.src.rpm ... snip ... Wrote: /usr/src/RPM/RPMS/noarch/mplayer-fonts-1.0-10mdk.noarch.rpm Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.1910 + umask 022 + cd /usr/src/RPM/BUILD + cd mplayer-fonts-1.0 + rm -rf /var/tmp/mplayer-fonts-buildroot + exit 0 Executing(--clean): /bin/sh -e /var/tmp/rpm-tmp.1910 + umask 022 + cd /usr/src/RPM/BUILD + rm -rf mplayer-fonts-1.0 + exit 0 # rpm -Uvh /usr/src/RPM/RPMS/noarch/mplayer-fonts-1.0-10mdk.noarch.rpm Preparing... ### [100%] 1:mplayer-fonts ### [100%] Are you sugesting I should'a used 'rpmbuild --rebuild mplaTab' ? FWIW, the system is as current as can be (cooker 10.2) 2.6.11-2mdkK74 preempt K7 gcc-3.4 (rpm-build-4.2.3-9mdk) From the rpm man page: LEGACY ISSUES Executing rpmbuild The build modes of rpm are now resident in the /usr/bin/rpmbuild executable. Although legacy compatibility provided by the popt aliases below has been adequate, the compatibility is not perfect; hence build mode compatibility through popt aliases is being removed from rpm. Install the rpmbuild package, and see rpmbuild(8) for documentation of all the rpm build modes previously documented here in rpm(8). Add the following lines to /etc/popt if you wish to continue invoking rpmbuild from the rpm command line: It then goes into a table that you can read for your self if you are interested. Mikkel # less /etc/popt /etc/popt: No such file or directory Do I need to create this file? an why? rpm -rebuild is still very much functional, even on 10.2 Yes, I read the man page. Well, on my 10.1 system, they are actualy in /usr/lib/rom/rpmpopt-4.2.2 and if I wanted to track it down, there is probably another file symlinked to it, that is defined in rpmrc, but I don't feel like going through all the effort. There are a lot of things that can be changed the same way, to customize the way rpm behaves. Mikkel -- Do not meddle in the affairs of dragons, for you are crunchy and taste good with Ketchup! Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] src.rpm headaches.
Hello, I thank you both for this information, but I'm not getting anything out of this package. the rpm --rebuild gives: error: kdeutils-3.2.3-28.3.101mdk.src.rpm cannot be installed the same happens with rpmbuild --rebuild (both as root and otherwise). I assume that the package is at fault and will look for another source. Another question I have, is why I urpmi --install-src yield nothing. Thanks, JHM On Saturday 19 March 2005 1:59 pm, Tom wrote: Greg Meyer wrote: On Saturday 19 March 2005 10:05 am, Tom wrote: James Henry Maiewski wrote: Hello, I downloaded kdeutils-3.2.3-28.3.101mdk.src.rpm to see what I could see, but when I try to install it, it says everything already installed. If these are supposed to go in /usr(/local)/src they are empty. How is the installation of .src.rpm files supposed to work? With an advance of thanks, James Henry Maiewski src.rpm's are not to be installed (tho they can be). You can compile the rpms contained in the src.rpm by doin (as root) 'rpm --rebuild kdeutils-3.2.3-28.3.101mdk.src.rpm' Not to be too picky, but technically, rpm is deprecated and rpmbuild --rebuild is preferred because it has been split into separate packages. hmmm... tell me more. # rpm --rebuild mplayer-fonts-1.0-10mdk.src.rpm ... snip ... Wrote: /usr/src/RPM/RPMS/noarch/mplayer-fonts-1.0-10mdk.noarch.rpm Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.1910 + umask 022 + cd /usr/src/RPM/BUILD + cd mplayer-fonts-1.0 + rm -rf /var/tmp/mplayer-fonts-buildroot + exit 0 Executing(--clean): /bin/sh -e /var/tmp/rpm-tmp.1910 + umask 022 + cd /usr/src/RPM/BUILD + rm -rf mplayer-fonts-1.0 + exit 0 # rpm -Uvh /usr/src/RPM/RPMS/noarch/mplayer-fonts-1.0-10mdk.noarch.rpm Preparing... ### [100%] 1:mplayer-fonts ### [100%] Are you sugesting I should'a used 'rpmbuild --rebuild mplaTab' ? FWIW, the system is as current as can be (cooker 10.2) 2.6.11-2mdkK74 preempt K7 gcc-3.4 (rpm-build-4.2.3-9mdk) the resulting rpms will then be found in /usr/src/RPM/RPMS/i586/ Just as a general rule it is not a good idea to compile src.rpms as root, because if the buildroot variable is not set, the package will actually get installed on your machine, so as a habit, it is safer to setup the RPM dir in ~/ and build as user. Mandrake is very good about this, but occasionally you get a 3rd party packager that forgets to set this and It's just a good habit. and you can bork the system. Two schools, an I'm in the other one ;) 'Sides the OP did cite a Mandrake rpm. More important to me would be direct newbies to always use Mandrake rpms, src.rpms included, to procure wanted apps or dependencies. More over to disdain corrupting their systems with anything 3rd party (includin drivers an apps, rpms or tarballs). Build as user all you want, but if you install closed source binary only taints on it, the precaution to only build rpms (or tarballs for that matter) as user is sort'a moot, borderin on ridiculous. Another example; 'rpm --rebuild --target athlon kdeutils-3.2.3-28.3.101mdk.src.rpm' will compile the rpms, athlon optimized, and place them in /usr/src/RPM/RPMS/athlon/ This is cool, and might be fun to experiment to see if this has any effect on your system. IME, no. But when I ocaisionally do build from source, I include athlon opts just for grins. Mostly kernels (as in 2.6.11-2mdkK74, compiled for athlon, preempt, 4gig ram support). I used Mdk's kernel-source rpm an changed the .config, mostly to gain preempt and support for 1gig of ram. An then only 'cause such a kernel wasn't avaible from Mandrake, pre-compiled. The src.rpm will build _all_ the rpms contained in the src.rpm. So if you only want to upgrade only kdeutils rpms you already have installed, cd to one of the above directories and use Just one small point about your use of terminology in order to clarify, you are compiling the source and building the rpm packages as they are specified in the src.rpm's spec file, not releasing already built things packaged together. It kind of sounds like they are being hatched instead of built the way you described it :) 'hatched'? not sure what you mean Greg. The 'F' switch in 'rpm -Fvh' will only upgrade existing packages on the system, not all packages included in the src.rpm. Good example would be 'xorg' which would create more than a dozen packages, but only about 7 of which are used on my system. Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] src.rpm headaches.
Mikkel L. Ellertson wrote: Tom wrote: Mikkel L. Ellertson wrote: Tom wrote: hmmm... tell me more. # rpm --rebuild mplayer-fonts-1.0-10mdk.src.rpm ... snip ... Wrote: /usr/src/RPM/RPMS/noarch/mplayer-fonts-1.0-10mdk.noarch.rpm Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.1910 + umask 022 + cd /usr/src/RPM/BUILD + cd mplayer-fonts-1.0 + rm -rf /var/tmp/mplayer-fonts-buildroot + exit 0 Executing(--clean): /bin/sh -e /var/tmp/rpm-tmp.1910 + umask 022 + cd /usr/src/RPM/BUILD + rm -rf mplayer-fonts-1.0 + exit 0 # rpm -Uvh /usr/src/RPM/RPMS/noarch/mplayer-fonts-1.0-10mdk.noarch.rpm Preparing... ### [100%] 1:mplayer-fonts ### [100%] Are you sugesting I should'a used 'rpmbuild --rebuild mplaTab' ? FWIW, the system is as current as can be (cooker 10.2) 2.6.11-2mdkK74 preempt K7 gcc-3.4 (rpm-build-4.2.3-9mdk) From the rpm man page: LEGACY ISSUES Executing rpmbuild The build modes of rpm are now resident in the /usr/bin/rpmbuild executable. Although legacy compatibility provided by the popt aliases below has been adequate, the compatibility is not perfect; hence build mode compatibility through popt aliases is being removed from rpm. Install the rpmbuild package, and see rpmbuild(8) for documentation of all the rpm build modes previously documented here in rpm(8). Add the following lines to /etc/popt if you wish to continue invoking rpmbuild from the rpm command line: It then goes into a table that you can read for your self if you are interested. Mikkel # less /etc/popt /etc/popt: No such file or directory Do I need to create this file? an why? rpm -rebuild is still very much functional, even on 10.2 Yes, I read the man page. Well, on my 10.1 system, they are actualy in /usr/lib/rom/rpmpopt-4.2.2 and if I wanted to track it down, there is probably another file symlinked to it, that is defined in rpmrc, but I don't feel like going through all the effort. There are a lot of things that can be changed the same way, to customize the way rpm behaves. Mikkel # less/usr/lib/rom/rpmpopt* bash: less/usr/lib/rom/rpmpopt*: No such file or directory # l /usr/lib/rom/rpmpopt* ls: /usr/lib/rom/rpmpopt*: No such file or directory # loci rpmrc (an alias for locate -i) /usr/lib/rpm/rpmrc /usr/lib/rpm/convertrpmrc.sh /usr/lib/rpmrc untouched by me ??? -- Tom Brinkman Corpus Christi, Texas Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] src.rpm headaches.
James Henry Maiewski wrote: Hello, I thank you both for this information, but I'm not getting anything out of this package. the rpm --rebuild gives: error: kdeutils-3.2.3-28.3.101mdk.src.rpm cannot be installed the same happens with rpmbuild --rebuild (both as root and otherwise). I assume that the package is at fault and will look for another source. Another question I have, is why I urpmi --install-src yield nothing. Thanks, JHM What happens if you run rpm --checksig kdeutils-3.2.3-28.3.101mdk.src.rpm? This will check the package. Mikkel -- Do not meddle in the affairs of dragons, for you are crunchy and taste good with Ketchup! Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] src.rpm headaches.
Tom wrote: Mikkel L. Ellertson wrote: Well, on my 10.1 system, they are actualy in /usr/lib/rom/rpmpopt-4.2.2 and if I wanted to track it down, there is probably another file symlinked to it, that is defined in rpmrc, but I don't feel like going through all the effort. There are a lot of things that can be changed the same way, to customize the way rpm behaves. Mikkel # less/usr/lib/rom/rpmpopt* bash: less/usr/lib/rom/rpmpopt*: No such file or directory # l /usr/lib/rom/rpmpopt* ls: /usr/lib/rom/rpmpopt*: No such file or directory # loci rpmrc (an alias for locate -i) /usr/lib/rpm/rpmrc /usr/lib/rpm/convertrpmrc.sh /usr/lib/rpmrc untouched by me ??? Well, my typing isn't too good today. (rom should be rpm). Fat fingers, and small keyboard.) Mikkel -- Do not meddle in the affairs of dragons, for you are crunchy and taste good with Ketchup! Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] src.rpm headaches.
On Saturday 19 March 2005 3:12 pm, Mikkel L. Ellertson wrote: What happens if you run rpm --checksig kdeutils-3.2.3-28.3.101mdk.src.rpm? This will check the package. Mikkel kdeutils-3.2-18.1.100mdk.src.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: GPG#22458a98) oh oh spaghetti-o! Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] src.rpm headaches.
James Henry Maiewski wrote: Hello, I thank you both for this information, but I'm not getting anything out of this package. the rpm --rebuild gives: error: kdeutils-3.2.3-28.3.101mdk.src.rpm cannot be installed the same happens with rpmbuild --rebuild (both as root and otherwise). I assume that the package is at fault and will look for another source. Another question I have, is why I urpmi --install-src yield nothing. --install-src looks to me like this would try an install the src.rpm. You really don't wanna do that Thanks, JHM # rpm --rebuild kdeutils-3.3.2-20mdk.src.rpm big snip Wrote: /usr/src/RPM/RPMS/i586/kdeutils-3.3.2-20mdk.i586.rpm Wrote: /usr/src/RPM/RPMS/i586/kdeutils-klaptop-3.3.2-20mdk.i586.rpm Wrote: /usr/src/RPM/RPMS/i586/libkdeutils1-klaptop-3.3.2-20mdk.i586.rpm Wrote: /usr/src/RPM/RPMS/i586/libkdeutils1-klaptop-devel-3.3.2-20mdk.i586.rpm Wrote: /usr/src/RPM/RPMS/i586/kdeutils-common-3.3.2-20mdk.i586.rpm Wrote: /usr/src/RPM/RPMS/i586/kdeutils-ktimer-3.3.2-20mdk.i586.rpm Wrote: /usr/src/RPM/RPMS/i586/kdeutils-kdessh-3.3.2-20mdk.i586.rpm Wrote: /usr/src/RPM/RPMS/i586/kdeutils-kjots-3.3.2-20mdk.i586.rpm Wrote: /usr/src/RPM/RPMS/i586/kdeutils-kdepasswd-3.3.2-20mdk.i586.rpm Wrote: /usr/src/RPM/RPMS/i586/kdeutils-kfloppy-3.3.2-20mdk.i586.rpm Wrote: /usr/src/RPM/RPMS/i586/kdeutils-kdf-3.3.2-20mdk.i586.rpm Wrote: /usr/src/RPM/RPMS/i586/kdeutils-kcharselect-3.3.2-20mdk.i586.rpm Wrote: /usr/src/RPM/RPMS/i586/kdeutils-khexedit-3.3.2-20mdk.i586.rpm Wrote: /usr/src/RPM/RPMS/i586/kdeutils-kedit-3.3.2-20mdk.i586.rpm Wrote: /usr/src/RPM/RPMS/i586/libkdeutils1-kedit-3.3.2-20mdk.i586.rpm Wrote: /usr/src/RPM/RPMS/i586/kdeutils-ark-3.3.2-20mdk.i586.rpm Wrote: /usr/src/RPM/RPMS/i586/libkdeutils1-ark-3.3.2-20mdk.i586.rpm Wrote: /usr/src/RPM/RPMS/i586/kdeutils-kcalc-3.3.2-20mdk.i586.rpm Wrote: /usr/src/RPM/RPMS/i586/libkdeutils1-kcalc-3.3.2-20mdk.i586.rpm Wrote: /usr/src/RPM/RPMS/i586/libkdeutils1-common-devel-3.3.2-20mdk.i586.rpm Wrote: /usr/src/RPM/RPMS/i586/libkdeutils1-common-3.3.2-20mdk.i586.rpm Wrote: /usr/src/RPM/RPMS/i586/kdeutils-ksim-3.3.2-20mdk.i586.rpm Wrote: /usr/src/RPM/RPMS/i586/kdeutils-kgpg-3.3.2-20mdk.i586.rpm Wrote: /usr/src/RPM/RPMS/i586/kdeutils-kwalletmanager-3.3.2-20mdk.i586.rpm Wrote: /usr/src/RPM/RPMS/i586/libkdeutils1-ksim-devel-3.3.2-20mdk.i586.rpm Wrote: /usr/src/RPM/RPMS/i586/libkdeutils1-ksim-3.3.2-20mdk.i586.rpm Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.22866 + umask 022 + cd /usr/src/RPM/BUILD + cd kdeutils-3.3.2 + rm -fr /var/tmp/kdeutils-3.3.2-20mdk-root/ + exit 0 Executing(--clean): /bin/sh -e /var/tmp/rpm-tmp.53096 + umask 022 + cd /usr/src/RPM/BUILD + rm -rf kdeutils-3.3.2 + exit 0 That was mostly for my own curiousity, specially since Greg an Mikkel have some misgiving about usin 'rpm --rebuild' All I can say is Works for Me an always has As you can see the src.rpm created more than two dozen kdeutils packages. More than I have with a normal install. This is why I cited 'rpm -Fvh' which would then only update the packages I'm usin. Now, James, when you installed the system did you select Development ? Without those additions to your system you probly can't compile anything. Other questions: are you just doin all this as an exercise? an why don't you just use Mandrakes' pre-compiled packages for kdeutils? IOW's, what are you tryin to accomplish? -- Tom Brinkman Corpus Christi, Texas Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] src.rpm headaches.
Mikkel L. Ellertson wrote: Tom wrote: Mikkel L. Ellertson wrote: Well, on my 10.1 system, they are actualy in /usr/lib/rom/rpmpopt-4.2.2 and if I wanted to track it down, there is probably another file symlinked to it, that is defined in rpmrc, but I don't feel like going through all the effort. There are a lot of things that can be changed the same way, to customize the way rpm behaves. Mikkel # less/usr/lib/rom/rpmpopt* bash: less/usr/lib/rom/rpmpopt*: No such file or directory # l /usr/lib/rom/rpmpopt* ls: /usr/lib/rom/rpmpopt*: No such file or directory # loci rpmrc (an alias for locate -i) /usr/lib/rpm/rpmrc /usr/lib/rpm/convertrpmrc.sh /usr/lib/rpmrc untouched by me ??? Well, my typing isn't too good today. (rom should be rpm). Fat fingers, and small keyboard.) Mikkel We're hijackin this thread ;) # loci rpmpopt /usr/lib/rpm/rpmpopt-4.2.3 /usr/lib/rpmpopt (symlinked to the above file) The lines you cited from the man page are already in /usr/lib/rpm/rpmpopt-4.2.3 Mandrake put 'em there, I didn't. I suspect you're goin on about 'generic' man pages that Mdk imports from other distros, mostly RH an Deb. Without re-writing them. All the while tho, the functions have already been taken care of by Mandrake. -- Tom Brinkman Corpus Christi, Texas Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] src.rpm headaches.
Tom wrote: That was mostly for my own curiousity, specially since Greg an Mikkel have some misgiving about usin 'rpm --rebuild' All I can say is Works for Me an always has I think the point is more that rpm --rebuild is calling rpmbuild to do the work. Because if this, if you do not have the rpm-build (10.1) or rpmbuild (old name) package installed, it will not work. Also, from what the man page says, it may not work in future releases of RPM. So it would be better to bet used to using rpmbuild --rebuild in place of rpm --rebuild. For people just starting to build RPMs, it would definitly be better to get them started using rpmbuild for building RPMs. Mikkel -- Do not meddle in the affairs of dragons, for you are crunchy and taste good with Ketchup! Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] src.rpm headaches.
Mikkel L. Ellertson wrote: Tom wrote: That was mostly for my own curiousity, specially since Greg an Mikkel have some misgiving about usin 'rpm --rebuild' All I can say is Works for Me an always has I think the point is more that rpm --rebuild is calling rpmbuild to do the work. Because if this, if you do not have the rpm-build (10.1) or rpmbuild (old name) package installed, it will not work. Also, from what the man page says, it may not work in future releases of RPM. So it would be better to bet used to using rpmbuild --rebuild in place of rpm --rebuild. For people just starting to build RPMs, it would definitly be better to get them started using rpmbuild for building RPMs. Mikkel OK, thanks Mikkel. I'll tryin keep an eye on it FWIW, out of curiousity I re-did kdeutils src.rpm with rpmbuild --rebuild kdeutils-3.3.2-20mdk.src.rpm Worked the same as 'rpm --rebuild'. BUT you're right, it's better to use pending changes. I'll mend my ways ;) Thanks for the heads up -- Tom Brinkman Corpus Christi, Texas Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] src.rpm headaches.
On Saturday 19 March 2005 01:59 pm, Tom wrote: 'hatched'? not sure what you mean Greg. I know what you meant, but I was just making light of the fact that you used the word contained when describing the src.rpm. I was trying to be funny. The src.rpm will build _all_ the rpms contained in ... This implies that the rpms are already there and you just have to let them out,, ie hatch them *cheesy grin* -- /g Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] src.rpm headaches.
On Saturday 19 March 2005 01:59 pm, Tom wrote: Greg Meyer wrote: Not to be too picky, but technically, rpm is deprecated and rpmbuild --rebuild is preferred because it has been split into separate packages. hmmm... tell me more. # rpm --rebuild mplayer-fonts-1.0-10mdk.src.rpm ... snip ... Wrote: /usr/src/RPM/RPMS/noarch/mplayer-fonts-1.0-10mdk.noarch.rpm Yes, I didn't say it wouldn't work, just that it is deprecated in favor of rpmbuild, although this has been explained much more clearly than I did by Mikkel in another post, so no use re-iterating. Just as a general rule it is not a good idea to compile src.rpms as root, because if the buildroot variable is not set, the package will actually get installed on your machine, so as a habit, it is safer to setup the RPM dir in ~/ and build as user. Mandrake is very good about this, but occasionally you get a 3rd party packager that forgets to set this and It's just a good habit. and you can bork the system. Two schools, an I'm in the other one ;) 'Sides the OP did cite a Mandrake rpm. More important to me would be direct newbies to always use Mandrake rpms, src.rpms included, to procure wanted apps or dependencies. More over to disdain corrupting their systems with anything 3rd party (includin drivers an apps, rpms or tarballs). Build as user all you want, but if you install closed source binary only taints on it, the precaution to only build rpms (or tarballs for that matter) as user is sort'a moot, borderin on ridiculous. Well, my philosophy is to inform people of the potential risks and let them make their own decisions. So instead of saying go ahead, do this, it works for me, I prefer to say these are the two ways of doing it and there are potential pitfalls of doing it one of those ways. Then let the user make an informed choice. I'm not trying to be argumentative, just helpful by providing good information and making a clarification where I thought it would be helpful. -- /g Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
Re: [newbie] src.rpm headaches.
Greg Meyer wrote: On Saturday 19 March 2005 01:59 pm, Tom wrote: Â Â 'hatched'? Â not sure what you mean Greg. I know what you meant, but I was just making light of the fact that you used the word contained when describing the src.rpm. I was trying to be funny. The src.rpm will build _all_ the rpms contained in ... This implies that the rpms are already there and you just have to let them out,, ie hatch them *cheesy grin* No! that's exactly what I meant. You did know that src.rpms are actually eggs, an once you crack'em open, a mystery of rpms pour out! ? ! hehehe Yeah you're right Greg, I should be more accurate and articulate in my wordin ... I've probly lived in Texas too long ;) ...an depend on a faith in newbies to discern. A faith I believe they deserve -- Tom Brinkman Corpus Christi, Texas Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com
