On 06/23/12 21:21, Ciaran McCreesh wrote: > There's been a move towards using slots for "clever" things that don't > fit the traditional way of how slots worked. Examples include the new > gtk2 / gtk3 handling and Ruby gems virtuals. > > Aside from being abusive, No, it solves a real problem. > this screws things up for Paludis users. -EDONTCARE, use a supported package manager > Paludis tends to bring in newer versions when possible (so that users > aren't stuck with an old GCC forever), and allows the user to select > when new slots are brought in. When suddenly a few packages are using > slots and versions to "mean" something other than what they used to, > this makes the feature unusable. > > Thus, as a quick workaround, I'd like to suggest adding a PROPERTIES > value called "funky-slots", which should be set on every version of any > package that uses slots in an unconventional manner. This probably > doesn't need EAPI control, since package manglers are free to ignore > PROPERTIES tokens. It won't solve the abuse, but it will allow the > impact upon users to be lessened. > Hackfix. Hardcode those packages in paludis if you need to. Cleaner and faster quick workaround until you can figure out a clean solution.
No reason to hack a working solution to bits, especially as it is rather easy to mask specific versions if they annoy you (as I do to keep my systems gtk3-free). The current solution is a side-effect of some upstreams being very confused, but I like the -r200/-r300 versioning fix for gtk apps.
