On Thu, 31 Oct 2002 17:35:56 -0000 (GMT) "Robin Bowes" <[EMAIL PROTECTED]> wrote:
# 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. Thats assuming you are using binary rpms. When you get into dealing with sourcerpms, or sources with a spec file then you do have to have some knowledge about software compiling. The BuildReq section is evoked when you issue a rpmbuild -ta or -ba, you never have to open up the spec file to make sure you have all that it requires, as it will tell you. # What it all boils down to is that I'd like to see reference to the # spec file in the rpm build instructions. man rpm # 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 think you need to read about RPMS a bit more. When you run rpmbuild -ta file.tar.gz it looks at the spec file, and checks for dependencies. Since you didn't have fam, it told you that you needed fam and fam-devel to continue. Thats BuildReqs in action. If you wanted to look at the spec file, you can. -- Jesse Keating j2Solutions.net Mondo DevTeam (www.mondorescue.org) Was I helpful? Let others know: http://svcs.affero.net/rm.php?r=jkeating ------------------------------------------------------- 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
