Thursday, February 02, 2023

Re: remove a few go libraries leaf ports

On 23-02-02 10:08:54, Omar Polo wrote:
> On 2023/02/02 20:00:44 +1100, Joel Sing <joel@sing.id.au> wrote:
> > On 23-02-02 09:35:32, Omar Polo wrote:
> > > These are a few ports that have no reverse deps (outside themselves)
> > > and that don't provide any binary, only the go code, and thus quite
> > > useless. nowadays a go port would just use the modules if depends on
> > > these.
> > >
> > > - devel/go-sys
> > > - security/go-crypto
> > > - security/go-ed25519
> > > - security/go-siphash
> > >
> > > textproc/go-text could go as well but since it provides bin/colcmp
> > > maybe someone uses it? (not that it couldn't be replaced with a
> > > proper -updated- port...)
> >
> > Thanks - I believe the list is actually larger, from when I last looked
> > at this:
>
> I already took care of some of them. These were just removed:
>
> > - devel/go-goptlib
> > - net/go-net
>
> and this updated last week to use modules
>
> > - devel/go-tools
>
> (gopls was moved to its own port.)

Ah, excellent. Thanks.

> so only these remains :)
>
> I'm happy to remove textproc/go-text too, if anyone is using colcmp it
> would be easy to re-add as standalone port.

Please go ahead and remove textproc/go-text as well.

> > - devel/go-sys
> > - security/go-crypto
> > - security/go-ed25519
> > - security/go-siphash
> > - textproc/go-text
> >
> > All of these are seriously dated and if anyone uses binaries from these
> > they're likely using 'go install'. And if someone wants it packaged then
> > it needs to be updated (and sufficiently maintained), in which case it
> > will use modules and hence not the current deps.
> >
> > I can't comment on the exact process, but I'm very much ok with removing
> > all of these, if you could add them to the list.

No comments:

Post a Comment