| 1 |
On Fri, Feb 03, 2006 at 10:19:18AM +0000, Francesco Riosa wrote: |
| 2 |
> A good solution should be to add the "multislot" USE flag to the ebuild |
| 3 |
> and let it to decide whenever make it slotted or not, sorry, this is not |
| 4 |
> viable, yes it's already used by other important packages but not well |
| 5 |
> supported by portage and should be used only in particular situations. |
| 6 |
[snip] |
| 7 |
> example: |
| 8 |
> |
| 9 |
> mysql-4.1.16-r[0..49] Need "+multislot" |
| 10 |
> mysql-4.1.16-r[50..99] Need "-multislot" |
| 11 |
> mysql-5.1.18-r[0..49] Need "+multislot" |
| 12 |
> mysql-5.1.18-r[50..99] Need "-multislot" |
| 13 |
NAK. Do not go the route of ranged revisions for specific features. |
| 14 |
|
| 15 |
If you go with multislot, you must make it work in ALL revisions. |
| 16 |
|
| 17 |
One of the reasons why is that portage does not support a limited |
| 18 |
ranged dep properly last I checked, so this is hard for everybody to |
| 19 |
deal with. |
| 20 |
|
| 21 |
-- |
| 22 |
Robin Hugh Johnson |
| 23 |
E-Mail : robbat2@g.o |
| 24 |
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 |
Archives