<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Ahh good point.. Fortunatly by including 'all the -devels' 98% is
covered.. What's probably missing from the list are things like doxygen
(i dont think anything requires it, but i know apr/httpd forinstance do
buildrequire it). But as i said, i think most of it is in there.<br>
<br>
I think you might've just inspired me to expand my script to pull in
.spec's too..<br>
<br>
.. Just brainstorming here, easiest way to get the .spec file for
installed packages would probably be to:<br>
<br>
source_pkg = `rpm -q <package> -qf "%{SOURCERPM}"`<br>
spec_file = `rpm -qpl /path/to/$source_pkg | grep ".spec"`<br>
rpm2cpio $source_pkg | cpio -iv $spec_file<br>
<br>
-- Chris<br>
<br>
Jeremy Katz wrote:
<blockquote cite="mid1085498197.8977.13.camel@bree.local.net"
type="cite">
<pre wrap="">On Tue, 2004-05-25 at 16:06 +0200, Chris Chabot wrote:
</pre>
<blockquote type="cite">
<pre wrap="">-d Include the *-devel packages for all packages in the list
(and it's dependencies). This is includes because i am a big fan of
having a system that could build it's self, it's updates and any other
source rpm's/tarbals you would download.
</pre>
</blockquote>
<pre wrap=""><!---->
Unfortunately, this doesn't tell you what you need to build. For that,
you need src.rpms and to analyze the BuildRequires (since BuildRequires
only show up as a Requires on a src.rpm)
Cheers,
Jeremy
</pre>
</blockquote>
<br>
</body>
</html>