1 |
On Mon, May 11, 2020 at 09:51:45AM -0400, Mike Gilbert wrote: |
2 |
> On Sun, May 10, 2020 at 5:16 PM William Hubbs <williamh@g.o> wrote: |
3 |
> > |
4 |
> > All, |
5 |
> > |
6 |
> > now that go 1.14.2 is stable, I want to remove the EGO_VENDOR support from |
7 |
> > go-module.eclass. |
8 |
> > |
9 |
> > This was kept when the EGO_SUM support was added on 4 Mar, with a qa |
10 |
> > warning advising people to migrate their ebuilds to EGO_SUM. |
11 |
> > |
12 |
> > This patch makes migrating mandatory by forcing ebuilds to die if they |
13 |
> > have EGO_VENDOR set and are using go-module.eclass. |
14 |
> > |
15 |
> > Thoughts? |
16 |
> |
17 |
> It seems like you're being very lazy about this. At a minimum, you |
18 |
> should do the following: |
19 |
|
20 |
I will respond to your points below, but first, I take offense to your |
21 |
accusation of me being lazy especially since it seems pretty obvious you |
22 |
didn't attempt to research my work before you said it. |
23 |
|
24 |
> 1. Search for affected packages. |
25 |
|
26 |
Done. |
27 |
|
28 |
> 2. Contact the maintainers, possibly via bug reports. |
29 |
|
30 |
Already done. If you look at the packages I have been doing this conversion for |
31 |
so far, you would see that most of them are maintained by myself, zac or |
32 |
not maintained at all. |
33 |
|
34 |
> 3. Give them a some time to convert their packages. |
35 |
|
36 |
No one has had issues with me doing the work myself, so that is what has |
37 |
been happening. Also, keep in mind that there was a public announcement |
38 |
made on this list about migrating go packages to the go-module eclass, |
39 |
and no one spoke out then against it. |
40 |
|
41 |
> 4. Mask any packages that do not get updated. |
42 |
|
43 |
There's only one I have masked so far and that was per the maintainer. I |
44 |
did post the lastrites but it looks like I need to forward it to -dev or |
45 |
re-post it, I will take a look again after I respond to this message. |
46 |
|
47 |
William |