On Tue, 2004-10-19 at 15:44, Michael van Elst wrote:
On Tue, Oct 19, 2004 at 02:29:41PM -0700, David M. Fetter wrote:
Well, in our last example problem, the installed instance of gcc was
simply a vanilla version with no additional options other than the
default. However we needed the f77
It seems that openpkg build doesn't recognize or handle properly rpms
that have been updated only with a new option. If I'm doing a full
rebuild from a source rpm then the specified options in the build file
are recongized and the various package along with dependencies are
rebuilt. However,
On Tue, Oct 19, 2004 at 10:20:35AM -0700, David M. Fetter wrote:
rebuilt. However, once we deploy the newly built binary rpms into our
repository to be pushed out to client systems the openpkg build doesn't
acknowledge such changes.
What do you mean with doesn't acknowledge such changes ?
On Tue, 2004-10-19 at 13:59, Michael van Elst wrote:
On Tue, Oct 19, 2004 at 10:20:35AM -0700, David M. Fetter wrote:
rebuilt. However, once we deploy the newly built binary rpms into our
repository to be pushed out to client systems the openpkg build doesn't
acknowledge such changes.
On Tue, Oct 19, 2004 at 02:29:41PM -0700, David M. Fetter wrote:
Well, in our last example problem, the installed instance of gcc was
simply a vanilla version with no additional options other than the
default. However we needed the f77 option so we rebuilt the package on
our build server,
