On Thu, 2004-10-21 at 08:45, David M. Fetter wrote: > 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 option so we rebuilt the package on > > > our build server, then placed the binary in our repository. When we > > > went out to the client servers, the build tools didn't see that the new > > > gcc version was compiled with this additional option or at least it > > > didn't upgrade anything or show that it needed to be upgraded. So > > > seemingly the build tools aren't acknowledging the changes. > > > > Did you tell the build tool on the client servers to use the f77 option ? > > Oh. I didn't realize you had to do that with the binaries. Silly me. > Thanks. That will most likely fix my problem.
Ok, so I added our custom ~/.openpkg/build file to all of our systems under root's account. There is a cron job in place to go out and fetch all updates via our local repository. However, it seems that when executing the updates via cron, openpkg still doesn't pick up the build options specified in the build file. We have an option change for openssh which isn't detecting due to this. Now, if I execute this update script manually as root it all works properly. Anybody have any ideas as to why this might be? -- David M. Fetter - UNIX Systems Administrator Portland State University - www.oit.pdx.edu "Only those who attempt the absurd can achieve the impossible."
signature.asc
Description: This is a digitally signed message part
