| 1 |
Michał Górny schrieb: |
| 2 |
> Hello, |
| 3 |
> |
| 4 |
> I have prepared a first draft of 'dynamic SLOT' specification. This is |
| 5 |
> my proposal in attempt to solve the problem of building packages for |
| 6 |
> multiple Python and Ruby versions. It could also be reused for multilib. |
| 7 |
> |
| 8 |
> The spec tries to explain the broad idea, and all problems relevant to |
| 9 |
> it. It also lists a few problems which are still unsolved and I think |
| 10 |
> they will cause the spec to change after hearing your ideas. |
| 11 |
> |
| 12 |
> To be honest, I tried to keep it as simple as possible. Please don't |
| 13 |
> say it doesn't solve all the world problems because it simply won't. |
| 14 |
> |
| 15 |
> I'm attaching a reStructuredText version of the spec. You can view it |
| 16 |
> rendered as a gist[1]. But please keep the replies on the list, rather |
| 17 |
> than forking the gist. |
| 18 |
> |
| 19 |
> [1]:https://gist.github.com/2943774 |
| 20 |
> |
| 21 |
|
| 22 |
Since you have not responded to my lines in IRC, i will repeat them here: |
| 23 |
|
| 24 |
First: How does the user see, which slots are possible and which ones |
| 25 |
are currently active and which are currently not selected? |
| 26 |
|
| 27 |
Beside that, it seems to solve things pretty similar to the proposed way |
| 28 |
in multilib-portage for cross-compiling (which could also be adapted for |
| 29 |
multi-slot languages) with different wording and with additional work |
| 30 |
for ebuild maintainers. And since my proposal already uses USE flags, |
| 31 |
things would not change visually for users of e.g. ruby or php. |
| 32 |
|
| 33 |
-- |
| 34 |
|
| 35 |
Thomas Sachau |
| 36 |
Gentoo Linux Developer |
Archives