Ciaran McCreesh posted on Sun, 02 Sep 2012 20:04:11 +0100 as excerpted: > The big issues you're ignoring: > > * What to do if a package has an SDEPEND upon cat/pkg[x] and the user > has cat/pkg[-x] installed, or if another package in the resolution > depends upon cat/pkg and the user hasn't specified USE=x. Similarly, > an SDEPEND upon >=cat/pkg-2.1 and the user has cat/pkg-2.0 (which is > in the same slot as 2.1) installed. The right answer is to force a > reinstall with [x] / force the upgrade, and for the spec to explicitly > require this from implementations, but *why* this is the case is > fairly subtle.
> * What use? blocks in SDEPEND actually mean. Again, there's a right > answer here: it's for when a particular suggestion requires the base > package to be built in a particular way. Reading here, the above "right answers" look self-evident to me, but I'm assuming the "somebody else did it so it looks simple" principle applies and I'm simply not seeing the too easy but wrong trap-answers. It would be quite helpful if you'd briefly describe them as you did the "right answers", along with (if it's not apparent given both them and right answers) why they're traps, as well. You mention the significant work it was to get these right for kbuilds and exherbo down-thread, and I'd imagine so. But with these "right answers" looking self-evident and no knowledge of the traps you had to avoid to get to them, it ends up looking far simpler than I imagine it was, and given that we're discussing specs for the gentoo solution to the same problem, having someone explicitly point out what and where the traps are in ordered to avoid them could be quite helpful indeed. Thanks. =:^) -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
