From: Stuart Henderson <stu@spacehopper.org>
Subject: Re: should we keep net/go-ipfs in ports?
To: Kirill Bychkov <kirby@linklevel.net>
Cc: ports@openbsd.org
Date: Fri, 6 Jun 2025 12:48:31 +0100

On 2025/06/06 13:02, Kirill Bychkov wrote:
> On Fri, May 30, 2025 00:19, Kirill Bychkov wrote:
> > On Thu, May 29, 2025 21:10, Stuart Henderson wrote:
> >> On 2025/05/29 14:26, Kirill Bychkov wrote:
> >>> On Wed, February 19, 2025 14:01, Stuart Henderson wrote:
> >>> > On 2025/02/19 04:48, Lydia Sobot wrote:
> >>> >> >I've noticed that official binaries for OpenBSD are available from
> >>> >> >upstream as you can see here
> >>> >> >https://docs.ipfs.tech/install/command-line/#install-official-binary-distributions.
> >>> >> >Also those are a newer version than the one we have in ports and they
> >>> >> >offer ipfs-cluster OpenBSD binaries as well, which we don't have in
> >>> >> >ports.
> >>> >> They don't have ARM64 binaries for *BSD, so purely personally I feel
> >>> like
> >>> >> maybe just updating the port might be better, and maybe adding the
> >>> cluster
> >>> >> binaries
> >>> >> However, shouldn't this port be renamed to kubo?
> >>> >
> >>> > the package was renamed to kubo in 2022, and packages rather than ports
> >>> > are the main user-facing interface for installing it. moving the port to
> >>> > a different dir loses cvs history so we don't usually bother. (I note
> >>> > that upstream hasn't renamed the binary either).
> >>> >
> >>> > there doesn't seem to have been much interest in this software on
> >>> > ports@. and it does seem like something where providing an old version
> >>> > is a bit of a disservice to users. many of the updates to this port
> >>> > have only been prompted by reports of it being broken. perhaps it
> >>> > would be better to remove if there's not an active maintainer.
> >>> >
> >>> > $ make test
> >>> > No regression tests for kubo-0.33.2
> >>> >
> >>> > cheat sheet for updating most go ports: bump MODGO_VERSION,
> >>> > "make modgo-gen-modules > tmp; mv tmp modules.inc; make makesum"
> >>> >
> >>> >
> >>> Hi,
> >>> Here is the patch to update kubo to latest version (0.35.0) with small
> >>> tweak in README.
> >>> Works fine for me. OK to commit?
> >>
> >> : $ IPFS_PATH=${LOCALSTATEDIR}/kubo doas -u _go-ipfs ${LOCALBASE}/bin/ipfs
> >> add
> >> /tmp/hello.txt
> >>
> >> doas doesn't preserve variables by default; rather than explaining
> >> about keepenv it would be preferable to pass it via env, e.g.
> >>
> >> $ doas -u _go-ips env IPFS_PATH=${LOCALSTATEDIR}/kubo ${TRUEPREFIX}/bin/ipfs
> >> \
> >> 	add /tmp/hello.txt
> >>
> >> (note it should be TRUEPREFIX i.e. "path where this port installs" not
> >> LOCALBASE).
> >>
> >> or /usr/local/bin is in the default path, so this is probably good
> >> enough:
> >>
> >> $ doas -u _go-ips env IPFS_PATH=/var/kubo ipfs add /tmp/hello.txt
> >>
> >>
> > Thanks for comments!
> > Patch with a fixed README. Now using "env" for doas and switched from
> > su -l -s .... to the same doas construction as stated in "Usage" srction.
> >
> 
> Ping

No opinion on the update itself, I don't use this.

README looks ok, the "ipfs init" change is mostly a noop but I think
probably easier for the typical user of this, and the "Usage" addition
does seem helpful, nitpicking I would remove the extra space in
"doas  -u"