On Wed, Mar 29, 2006 at 02:50:16PM -0800, David M. Fetter wrote:

> detail.  I'm just curious if it would be possible to modify openpkg
> tools so that it only rebuilds and installs dependent rpms if it in the
> BuildPreReq but not in the PreReq.

BuildPreReq is what is necessary to build a package from sources.

PreReq is what is necessary to install a package and this is the only
requirement that is stored in a binary package.

You may ignore the PreReq only if you are not going to install
the package, which is only possible for leaf packages that
are not dependencies of other packages. This might be of some
use for build farms, but it won't help you.


> Let me explain the dilemma so that it is (hopefully) understood.  I will
> use an example using the latest sendmail security fix.  When the fix is
> released, obviously, sendmail needs to be rebuilt and deployed.  In
> addition to rebuilding sendmail, openpkg tools sees various other rpms
> as also needing to be rebuilt then reinstalled due to static library
> linking.  For our environment, this includes: dk-milter; imapd; inn;
> mailman; majordomo; mapson; mimedefang; nagios; nail; nn; pine; pks;
> qpoper; pb4sd; and, shiela.  Now this isn't that many really, but how
> many of these actually need to be rebuilt and reinstalled?

Most probably only the milter. Everything else is probably just
using the sendmail binary later.

However, even the 'use' of the sendmail binary could, in theory,
require a rebuild or at least a reinstall, e.g. when a package checks
the sendmail version or feature list at build or install time.

You are right, the problem is in the requirements. However, the
problem is that we cannot express all facettes of a requirement.
You might even need a full matrix of package relations: "when
sendmail gets rebuilt then rebuild dk-milter, also reinstall imapd,
but only when the sendmail package indicates a new major version".


Greetings,
-- 
                                Michael van Elst
Internet: [EMAIL PROTECTED]
                                "A potential Snark may lurk in every tree."
______________________________________________________________________
The OpenPKG Project                                    www.openpkg.org
Developer Communication List                   openpkg-dev@openpkg.org

Reply via email to