Comment 15 for bug 316247

I've put some thought into this problem, and I'm not sure this is the best way to do it in the end. There are some tags for which it makes sense to attach semantic meaning, like "paid," which is another big problem for a lot of Sparkle's clients (though not Transmission, of course!)

Llike: you want people using 3.0b3 to get notified of their free update to 3.0 (to thank them for testing), but you don't want people using 2.5 to get that. Futhermore, what if you want to issue a critical security update to 2.5 (call it 2.5.1) that they should get, but 3.0 shouldn't see that update?

I think you need a graph, basically. I was thinking posets with labels. Labels could be "sticky" or not, potentially applying to incident edges coming from a vertex with that label. This would be useful for the "paid" label.

So between these hesitations and my continued promise that 1.5 is feature-frozen, I think this needs to wait.

It's maybe not a bad idea to get this kind of thing out there, though. And you can! Just branch Sparkle and apply your changes; it'll appear in Sparkle's main launchpad page for other people to merge in if they like.