On Thu, Sep 04, 2003 at 12:58:03AM +0200, Matthias Kurz wrote:
>
> So, shouldn't "openpkg build" have assumed the -U option in any case,
> given in the command line or not ?
There is no difference between a -U on the command line and a -U
in the .openpkg/build file.
A can only guess that you already had a current version of pkg1
installed, so the first build did nothing to pkg1 and thus did
not pull up any of the dependencies.
When you deleted pkg1 it had to be built from scratch and this
triggered checks to all dependencies including the bootstrap
package.
You can see the decision-making process in the output of 'openpkg build'.
E.g. a
# source for openpkg is openpkg-20030903-20030903
Somewhere the target 'openpkg' is touched, the heuristic decides
that this refers to 'openpkg-20030903-20030903'.
# make installs openpkg-20030903-20030903 for openpkg
The target 'make' requires installation of the target 'openpkg'
and uses the specific 'openpkg-20030903-20030903' package.
# rebuilding openpkg (update)
Installing target 'openpkg' requires a _rebuild_ (i.e. there is already
an openpkg package installed) and the prime reason for this is that
this is an update to a higher (or different) version.
# adding openpkg-20030903-20030903 to list
The rpm commands to build and install the openpkg-20030903-20030903
package are added to the generated script.
Greetings,
--
Michael van Elst
Internet: [EMAIL PROTECTED]
"A potential Snark may lurk in every tree."
______________________________________________________________________
The OpenPKG Project www.openpkg.org
User Communication List [EMAIL PROTECTED]
