On 23.06.2012 15: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, this screws things up for Paludis users. > 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. >
Did you read what you wrote and thought about what you request from others? Probably you better should. I can't see any good and more importantly, sufficient description of the problem. There is some vague hint, that paludis is not able to solve dependency chains correctly, but this is something I might got wrong from your mail. An example: "...slots and versions to "mean" something other than what they used to,..." is completely useless without a description of what SLOTS are about and how the should be used. And what is the wrong usage you can find; examples are necessary here for understanding. And your approach (a workaround called "funky-slots") to tackle this what-ever-the-problem-really is, doesn't fit to anything you want from others. To me, it doesn't solve the root cause, but actually I can't judge this, because I am missing a description of what is really going wrong. Don't behave in a way, which you disallow for others. justin
signature.asc
Description: OpenPGP digital signature
