On 01/24/2014 01:15 AM, Les Mikesell wrote:
On Thu, Jan 23, 2014 at 5:50 PM, Ljubomir Ljubojevic centos@plnet.rs wrote:
On 01/23/2014 05:39 PM, Les Mikesell wrote:
The big question is whether there is a way to keep a dependent/related package from updating until everything has been tested together when the packages are managed independently in separate repos.
If you compile package that depends on particular version:
Requires: <deppackage1> = 0.8.1
then yum will protest if you try to update newer deppackage1 package. Error will appear, and until you satisfy it nothing will happen.
Yes that could work, but it is not very efficient either. It should be rare for the update to break things but doing that would force you to update every related package after testing just to let the dependency advance even if no changes are required. Which again would make a flurry of traffic in the repositories and mirrors.
--
That is why I pushed for priorities. Everything is dynamic and server/infrastructure/repository side and no package rebuilding, just moving them little, and it should be possible to do it automatic (protection) with git/koji. No amount SCL's and overthinking will beat it's simplicity and universality.