On Mon, May 11, 2020 at 09:51:45AM -0400, Mike Gilbert wrote:
> On Sun, May 10, 2020 at 5:16 PM William Hubbs <willi...@gentoo.org> wrote:
> >
> > All,
> >
> > now that go 1.14.2 is stable, I want to remove the EGO_VENDOR support from
> > go-module.eclass.
> >
> > This was kept when the EGO_SUM support was added on 4 Mar, with a qa
> > warning advising people to migrate their ebuilds to EGO_SUM.
> >
> > This patch makes migrating mandatory by forcing ebuilds to die if they
> > have EGO_VENDOR set and are using go-module.eclass.
> >
> > Thoughts?
> It seems like you're being very lazy about this. At a minimum, you
> should do the following:
I will respond to your points below, but first, I take offense to your
accusation of me being lazy especially since it seems pretty obvious you
didn't attempt to research my work before you said it.

> 1. Search for affected packages.


> 2. Contact the maintainers, possibly via bug reports.

Already done. If you look at the packages I have been doing this conversion for
so far, you would see that most of them are maintained by myself, zac or
not maintained at all.

> 3. Give them a some time to convert their packages.

No one has had issues with me doing the work myself, so that is what has
been happening. Also, keep in mind that there was a public announcement
made on this list about migrating go packages to the go-module eclass,
and no one spoke out then against it.

> 4. Mask any packages that do not get updated.

There's only one I have masked so far and that was per the maintainer. I
did post the lastrites but it looks like I need to forward it to -dev or
re-post it, I will take a look again after I respond to this message.


Attachment: signature.asc
Description: PGP signature

Reply via email to