On Friday 09 January 2004 11:35 am, Warren Post wrote: > If I decide to keep the source after building the RPM, it belongs in > /usr/local/src -- correct? And is there any reason to save the source?
Since you have the tarball as well as the package, I can't imagine why you would keep the source. Given the rate of development, it probably won't be a month or two before a new version comes out. If you need to reinstall for some reason, you have the RPM or tarball to rebuild. If you upgrade other packages fairly often, it is possible you might have to rebuild anyway since dependencies on your machine may have changed. > Charlie suggested in an earlier post that "If you're building RPMs from > tarballs you'll want to set up a build directory and add that as a local > source as well. Then you can install with urpmi from there...", which > sounds like a good idea. Well, checkinstall builds and then installs the RPM that it builds unless you change the default behavior. So, once The RPM is built, it is already installed on that machine, there should be no reason to add the dir to sources unless you just want it to be there for reinstall. Unless I am being dense and missing something obvious. > Yet checkinstall does not place the RPMs it > creates in a single directory but rather in several subdirectories under > /usr/src/RPM/RPMS/, classified by architecture. I am tempted to find how > to change checkinstall's behavior to place RPMs in a single directory > and follow Charlie's advice, but before I do I'd like to understand what > the logic is in having RPMs for different architectures in different > directories. Probably to make sure that you don't inadvertently overwrite an existing package with similar or the same name structure. An easy way to get everything in one diretory would be to create a script to call checkinstall and have the script copy the finished RPM out of the dir and into a storage directory for safekeeping. In fact, it wouldn't be hard to simply create a script that finds all .rpm's in /usr/src/RPM/RPMS and moves all of them to a central repository. Then just call that script after checkinstall is done. > This issue becomes more relevant considering that I also download > pre-rolled RPMs and want to save them in the same place, and those RPMs > come in different architectures (at the moment, I have RPMs for i386, > i586, and noarch). It would be more convenient for me to have all my > RPMs (both pre-rolled and those I rolled myself, regardless of > architecture) in one place, and so be able to define one local source > for urpmi rather than many. Again, since the package is already installed, there would be no need to reinstall the new RPM, unless you just wanted to check it first or unless you need to force the install for some reason. A script would move the new RPM for you into a central repository. -- Bryan Phinney Software Test Engineer
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
