On Tue, 2005-02-22 at 07:24 -0800, Alan Hagge wrote: > Hopefully the issue with this should be obvious...I don't want to have > to modify (or have my less-familiar co-workers modify) and push to 100+ > clients a modified config file every time we override a package provided > by a repo with one of our own. Also, if we add a new repo, we don't > want to have to comb through what it provides to check whether it's > providing the same things that our "custom" repo is providing in order > to tweak include/exclude settings. I just want to be able to say "if > this repository provides a package, its version overrides all others, > including newer versions". > > Any other options? no, not really. Making one repo's packages 'better' even if the packages are not higher versions is just adding in a super-epoch. I'm not sure that's a good move for: 1. sanity of code 2. sanity of users 3. long term maintainability of depsolver. -sv
