Ah-ha - by including the source repository in the binary repository I get the behavior I want. "openpkg build" looks at the source rpm's but does not end up using them. Cool! I will probably check the output on the end machine to make sure a rpm --rebuild is never attempted.
Martin > -----Original Message----- > From: Michael van Elst [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, February 05, 2003 3:04 PM > To: [EMAIL PROTECTED] > Subject: Re: openpkg build -U ignores binary RPM's > > > On Wed, Feb 05, 2003, Andrews, Martin wrote: > > Hi, > > > Without the -U option openpkg build will happily use binary > RPM's that it > > finds, either local in RPM/PKG or in the specified > repository. With -U it > > seems to always force rebuild from source. I would like to > use "openpkg > > build -U" on most all my hosts so they get the latest > versions from my > > locally maintained binary RPM repository (most end machine > should never be > > compiling). Am I mis-using the openpkg tool or is this a bug? > > That's a feature. > > When one package is rebuilt this triggers updates of "reverse > dependencies" > that must be rebuilt to catch changes in the first packages (like a > statically linked library). > > But you are right, openpkg-tool takes a very safe road and rebuilds > too often. However, the package specifications do not contain all > dependency information and therefore even with a smarter openpkg-tool > you would see rebuilds that are not strictly necessary. > > Greetings, > -- > Michael van Elst > [EMAIL PROTECTED] > ______________________________________________________________________ > The OpenPKG Project www.openpkg.org > User Communication List [EMAIL PROTECTED] > ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List [EMAIL PROTECTED]
