seth vidal wrote: > Okay, I'm losing my mind on this so I'm going to write pseudo-code of > what should be happening for this dep presentation. Everyone who can > understand this, please respond:
I can understand it! Seriously, it all seems sane. Though it did get me thinking: We install/remove etc "physical" packages, but during depsolving, we're concerned with just the provides/requires, etc. I wonder if there is anything to be gained by mostly ignoring the actual packages during depsolving, and only looking at the prco. This way, you might remove a package, but if a given provides comes from something else, you won't have to care about it. I'll see if I can actually make any sense of this, but I'll do it much later :) -James PS you're going to write any missing bits using Test-Driven Development, right?
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Yum-devel mailing list [email protected] https://lists.dulug.duke.edu/mailman/listinfo/yum-devel
