| 1 |
On Sun, May 10, 2020 at 5:16 PM William Hubbs <williamh@g.o> wrote: |
| 2 |
> |
| 3 |
> All, |
| 4 |
> |
| 5 |
> now that go 1.14.2 is stable, I want to remove the EGO_VENDOR support from |
| 6 |
> go-module.eclass. |
| 7 |
> |
| 8 |
> This was kept when the EGO_SUM support was added on 4 Mar, with a qa |
| 9 |
> warning advising people to migrate their ebuilds to EGO_SUM. |
| 10 |
> |
| 11 |
> This patch makes migrating mandatory by forcing ebuilds to die if they |
| 12 |
> have EGO_VENDOR set and are using go-module.eclass. |
| 13 |
> |
| 14 |
> Thoughts? |
| 15 |
|
| 16 |
It seems like you're being very lazy about this. At a minimum, you |
| 17 |
should do the following: |
| 18 |
|
| 19 |
1. Search for affected packages. |
| 20 |
2. Contact the maintainers, possibly via bug reports. |
| 21 |
3. Give them a some time to convert their packages. |
| 22 |
4. Mask any packages that do not get updated. |
Archives