| 1 |
> Consider slots. I'm sure I've read that slots are used to allow multiple |
| 2 |
> ... versions? configurations? of the same package to be installed. It was |
| 3 |
> gradually dawning on me, that it's the developer who specifies the slot. |
| 4 |
> Now, I can't figure out what use case that benefits, but the ability to |
| 5 |
> have slots react to realities at a particular installation see to me to |
| 6 |
> make a lot of sense. So, there must be something basic that I don't |
| 7 |
> understand. |
| 8 |
> |
| 9 |
|
| 10 |
Multiple versions. Some software only works with a specific version of a |
| 11 |
dependency, so to ensure wide coverage of dependencies, multiple versions |
| 12 |
of the same software is required. |
| 13 |
|
| 14 |
Eg, some software may only work with python version 2.7 and other software |
| 15 |
may only work with python 3.6. If both versions of python are still being |
| 16 |
software maintained, an author may decide its not their top priority to |
| 17 |
re-write their software that's based on 2.7 to work with 3.6. |
Archives