1 |
There's been a move towards using slots for "clever" things that don't |
2 |
fit the traditional way of how slots worked. Examples include the new |
3 |
gtk2 / gtk3 handling and Ruby gems virtuals. |
4 |
|
5 |
Aside from being abusive, this screws things up for Paludis users. |
6 |
Paludis tends to bring in newer versions when possible (so that users |
7 |
aren't stuck with an old GCC forever), and allows the user to select |
8 |
when new slots are brought in. When suddenly a few packages are using |
9 |
slots and versions to "mean" something other than what they used to, |
10 |
this makes the feature unusable. |
11 |
|
12 |
Thus, as a quick workaround, I'd like to suggest adding a PROPERTIES |
13 |
value called "funky-slots", which should be set on every version of any |
14 |
package that uses slots in an unconventional manner. This probably |
15 |
doesn't need EAPI control, since package manglers are free to ignore |
16 |
PROPERTIES tokens. It won't solve the abuse, but it will allow the |
17 |
impact upon users to be lessened. |
18 |
|
19 |
-- |
20 |
Ciaran McCreesh |