Caches are dependent on superclass versions
I noticed an odd issue a while ago with configtool being masked for some reason on the old profile. I figured it was a false positive in conflict detection and never got around to looking into it.
But now, when looking for that as I test an improvement to conflict detection, I noticed that switching to a 2.0
profile for openmw after using a 3.0
profile is broken due to configtool being masked (because of the dependency issue I'm fixing it sometimes gives the wrong reason), but only because the pybuild cache cached the packages with common/mw-2
(masked on 2.0
), which adds a dependency on vfs-rebuild
, which depends on >=configtool-0.10 (which is masked). With the 2.0
profiles it should be using common/mw-1
. Clearing the cache fixed the issue and the error disappeared.
Invalidating the profiles if the superclass list doesn't match would be helpful, but it doesn't really solve the issue that different prefixes may use different superclasses, leading to differences in the cache. Maybe the caches need to be separate for each prefix rather than having a shared package cache for each repository.