On Tuesday 14 October 2003 03:21, Tom Allison wrote:

I'm trying to build an RPM package in SuSE using as much of the SuSE provided stuff that I am able to.

Part of this is to help someone evaluate SuSE as a replacement for his business. The easier it is for him, the better the chances of him using SuSE -- he's sick of the alternatives and wants to find a good Linux based solution for home and office.

I'm trying to install Courier-Imap on SuSE 8.2 I have the courier-source tarball (courier-0.43.2) and have installed db-devel and cyrus-sasl2-devel and am in the process of getting through an initial ./configure make make check

process in one window. This is to see if I have all the necessities to actually get it to compile.

It fails at 'make check' with tlspasswordcache.h:18: warning: `tlspasswordcace_h_rcsid` defined but not used make[1]: *** [tlspasswordcache.o] Error 1 make[1]: Leavig directory `/home/tallison/courier-0.43.2/tcpd` make: *** [check-recursive] Error 1

So I guess I'm still missing something... tcpd devel packages? I would have expected a failure at 'make'. I'm not sure what the Fix is here. I am using GNU Make 3.8.0

But I really want to be able to build up an RPM and ship it to him or have him build his own. This is part two.

But I keep getting stuck on the same section of the 'build --clean --rpms /mnt/' process:

I put all the rpm modules on the CD's on a seperate hard drive and mounted it at /mnt/ -- this solved a problem I was having with not being able to find fillup.rpm. I suspect it also solved most of my other problems I was having as well.

Now I get to a point where the output says:

Updating etc/sysconfig/suseconfig... preinstalling readline... preinstalling rpm... [...] preinstalling pam-modules... preinstalling permissions... Updating etc/sysconfig/security... ..aaa_version.rpm non found. Ignoring... ..................can not find cyrus-sasl.rpm... exit.

And that's all she wrote. Now, the problem that I have is that there is no cyrus-sasl.rpm package, only cyrus-sasl2. I believe that this is the problem here. But I'm not sure how to go about getting this sorted out.

HI Tom. As far as the pswrd in the tcp daemon requirements for the package I am not experienced enough in that arean to help you. However, on the issue of making a tarball into an rpm (and a distro/arch/machine specific rpm) then you can use "check install" program, it's on the disks (at least for 8.2, perhaps earlier IIRC). One you have ironed out the problems instead of make install you use check install instead. It installs the tarball but also makes an rpm (not a virtual but real rpm) in order to have it be accessible for the rpm database and therefore rpm can check dependencies, uninstall, yada yada, etc... But you'll have an rpm you can save, ship, install on other systems. So the routine would look like this: ./configure make (or make clean, dep, whatever) check install program opens, asks you a series of straight forward question like date, version, name, etc. installs the tarball/makes rpm. If you have done the tarball correctly, then if you ever need to remove or reinstall or whatever you have the rpm for you system and rpm -e <package name> and it's out. One thing to keep in mind however is that tarball, package compilation may be tailored for you system, but may present problems on other systems. Often times not but it could occur, regardless of archectectures being similar ( x86-32 but with different mobos, and sysconfigs) it may present problems in some cases. I find check install helps out emensely, especially to avoid the mixed tarball/rpm conundrum situation wherein rpm insists a package is not present when you know damn well it is, but as a tarball - RPM is blind to tarballs. Check install fixes this situation overall. HTH, Curits.