#47 Meeting topic: to keep or not to keep golang-x-build
Closed a year ago by gotmax23. Opened 2 years ago by eclipseo.

See https://bugzilla.redhat.com/show_bug.cgi?id=2045667

TL;DR;

Nothing depends on it.

github.com/golang-migrate/migrate/v4 requires a heap of new deps, so far around 30.

On the other hand it's a binary package, so maybe some people use it? Not sure, it's pretty Golang dev building specific.

I don't recall for what it was used for before.

If we cut it, there's probably tons of deps that can be deleted too, the whole modernc stack I believe is only used by this.

I don't mind doing the work of keeping it alive, but currently I'm focused on Docker.


+1 to remove it, but could be proposed as a F38 self-contained change and make people aware of the change.

If it's directly removed, it can be always restored.

Metadata Update from @gotmax23:
- Issue untagged with: meeting

2 years ago

This package has been retired due to FTI.

Metadata Update from @gotmax23:
- Issue status updated to: Closed (was: Open)

a year ago

Login to comment on this ticket.

Metadata