On Fri, 2005-09-09 at 15:29, Mike McCarty wrote: > Bryan J. Smith wrote: > > Les Mikesell <lesmikesell at gmail.com> wrote: > > > >>Please explain what would go wrong if yum simply ignored > >>the presence of files newer than a specified date. > > > > > > No offense, but build a YUM repository and you'll know > > _exactly_ why we think you are _clueless_ in this thread. > > [snip] > > People who have never had kids make statements which begin > "All you have to do is...", while the real parents are > hanging on by their fingernails just trying to survive. > > Maybe something a little bit similar is happening here? > > Mike If it was "easy" then anyone would be able to do it. :) The answer has been given several times, build and maintain your own repos. The production build repo will only have those packages you have tested and released. You can then build or update existing systems to that level by simply pointing to the production build repo. You would also have a test repo (possibly more than one) which would be used for testing new updates. Once you have a set that have passed QA you sync your production repo with the certified test repo and update your production systems. This is something you have to manage yourself. I don't know why you would trust an external repo to update your production systems in the first place. This would be a carefully controlled process that would be run from internal servers. You would only pull the latest release into a test environment from external repos. This eliminates potential issues with repos having problems, network issues, etc. And gives you the control over what is installed on your production systems. This is not an easy thing. It takes organization and work to setup, operate, and manage a large number of servers to strict standards. I withdraw now to watch the rest of this continuing saga unfold. :)