| 1 |
On 4/21/20 6:50 AM, Michał Górny wrote: |
| 2 |
> I realize Go is not isolated here. It's just brought as one major |
| 3 |
> example. Rust is no better. All these shiny 'write and forget' |
| 4 |
> languages share the same problem. Pay for some work hours, get |
| 5 |
> a working product, deploy it and forget unless customers want more |
| 6 |
> features. |
| 7 |
> |
| 8 |
> Today these languages are still young and the problems can be considered |
| 9 |
> largely theoretical. But some day -- well, unless all the cool kids |
| 10 |
> manage to move on to next shiny new language before then -- this will be |
| 11 |
> a major catastrophe. |
| 12 |
|
| 13 |
Looking into an old language (25 years old): php |
| 14 |
|
| 15 |
So many security problems... |
| 16 |
|
| 17 |
Just a few essential ebuilds exists in ::gentoo and being very well |
| 18 |
maintained by Gentoo. |
| 19 |
|
| 20 |
I think the approach to the new languages have the same requirement. |
| 21 |
Minimizing the ebuilds to the required ones would allow to minimize the |
| 22 |
effort. Then we can use an overlay to deliver all other software that |
| 23 |
would be useful. |
| 24 |
|
| 25 |
So the goal in this cases would be to define the right sieve about those |
| 26 |
libraries and tools that are required to all and that fits in package |
| 27 |
maintenance procedures, so it could be merged into ::gentoo. |
| 28 |
|
| 29 |
But don't forget the tooling available to the overlays development, |
| 30 |
where another abstraction layer takes place, since it's focused on a |
| 31 |
specific target and not all community in main ::gentoo. That's why I |
| 32 |
consider go-module as a very cleaver solution since it gives a hybrid |
| 33 |
solution connecting immutable delivery model into the mutable reality. |
| 34 |
|
| 35 |
The PR present in this subject is related to missing eclass for JVM |
| 36 |
languages, to define the common procedures to use those languages and |
| 37 |
available builders. |
Archives