Jesse, > On Wed, 30 Oct 2002 23:06:38 -0000 (GMT) > "Robin Bowes" <[EMAIL PROTECTED]> wrote: > > # For example, somewhere in the RPM build instructions, it wouldn't be > # unreasonable to say "In order to build this package you need the > # following packages installed: blah, blah, FAM, blah" > # > # After all, it's *optional*, so if I'm building from source > # (./configure ; make ; make install) then the configure script will > # detect that I don't have (for example) FAM installed and alter the > # build config accordingly. > > You mean the Build Requires: part of the spec file? lists all the > packages that you would need to build the whole thing. What more do > you want?
The rpm build instructions say: "To build a binary RPM package, enter: rpm -ta courier-imap-1.4.6.tar.gz" They also say: "IMPORTANT: even though building an RPM saves you the headaches of manually compiling the code, you should still read the INSTALL file as it contains many important details you need to know." There is no mention of the spec file in the INSTALL file. So, unless I extract the tarball and a. extract the tarball, and b. know what a spec file is, and c. know what to look for in the spec file, then I will never know about the Build Requires section. Let's face it, one of the main attractions of the rpm paradigm is that it means that, ahem, less technically adept people can still build and install software. So potentially, the users who are perhaps most likely to be using the rpm are those that are least likely to know about the BuildPreReq section in the spec file. What it all boils down to is that I'd like to see reference to the spec file in the rpm build instructions. Ideally, I'd like to see a list of build dependencies as well, but I appreciate that would introduce additional maintenance activities to ensure the spec file and the build instructions are in sync. I hope that makes my point clear. R. -- Robin Bowes | http://robinbowes.com ------------------------------------------------------- This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
