<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<p><span class="mono wrap nohighlight">We now have a new command to
test a package for its build dependencies. It should be used
when ever you upversion a package, or make significant changes
to it's build scripts (spec files, make files, auto-config ...)<br>
</span></p>
<p><span class="mono wrap nohighlight"> build-pkgs --dep-test
<pkg></span></p>
<p><span class="mono wrap nohighlight"><span class="mono wrap
nohighlight">It should be used when ever you upversion a
package, or make significant changes to it's build scripts
(spec files, make files, auto-config ...)</span></span></p>
<p><span class="mono wrap nohighlight"><span class="mono wrap
nohighlight"></span>Note: This should only be used following a
full build-pkgs. i.e. You need to be sure that an dependencies
that we also build are available.<br>
</span></p>
<p><span class="mono wrap nohighlight">One might think that if your
package passes a full build (</span><span class="mono wrap
nohighlight"><span class="mono wrap nohighlight">build-pkgs),
that you are safe, but this is NOT the case. When doing a
full build, we don't wipe the build environment clean between
packages. This means that the environment might (or might
not) have a tool or library present that your package needs,
but fails to list as a BuildRequires in its spec file. It
will build successfully one time, but night not build the
next. It all depends on what packages were scheduled to build
in the same environment before the package of interest.</span></span></p>
<p><span class="mono wrap nohighlight"><span class="mono wrap
nohighlight"><span class="mono wrap nohighlight">The
--dep-test option rebuilds just one package in a clean
environment, providing an effective test of the
BuildRequires for your package.<br>
</span></span></span></p>
</body>
</html>