The idea behind RPM is that you wrap the configure/make process with an RPM spec file, and let RPM do it, then package up the resulting files. Of course, making the spec file is a project in itself.
If you know all of the files that make up your package, you COULD make a skeleton spec file and "fake out" RPM to think you have a package, but that's almost as much trouble as doing it properly. I won't get into details here, but there's an excellent book on RPM available. "Maximum RPM" by Edward Bailey. > -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Aria Bamdad > Sent: Wednesday, February 18, 2004 9:34 AM > To: [EMAIL PROTECTED] > Subject: [LINUX-390] RPM question > > > Hi, > > If I install a package using the configure/make method, how > do I tell RPM > that the package is installed so that it will know about it? > > Thanks. > ============================================================================== If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail. <http://www.ml.com/email_terms/> ==============================================================================
