On Fri, Apr 21, 2023 at 10:47:24AM +0200, Omar Polo wrote: > On 2023/04/21 10:10:33 +0200, Theo Buehler <t...@theobuehler.org> wrote: > > On Fri, Apr 21, 2023 at 10:09:41AM +0200, Theo Buehler wrote: > > > A small utility without dependencies except go. It is therfore trivial > > > to install this by hand but job thought it would be useful to have it as > > > a port, so here we go. > > > > > > The Makefile has more handrolled things than I would like. go.port.mk is > > > an incomprehensible mess and it made me waste more than enough time for > > > this trivial thing. If there's a better way for anything, please let me > > > know. > > > > > > It is unlikely that this will ever see official releases, so I refrained > > > from prepending 0.0. to the date because I find this very ugly and hacky. > > > If this leaf port needs to bump EPOCH, so be it. > > > > > > [...] > > can be greatly semplified using MODGO_MODNAME and MODGO_VERSION, then > go.port.mk will take care of fetching, building and installing the > correct things (ok, sometimes it builds/installs more than > necessary, not the case however.) > > I've got the version number by running 'go get $url' in a dummy go > project and looking at the output. There's a way to do that easily > with 'go list' but I always forgot ^^"
Thank you. I'm not convinced this is simpler. Is the Makefile superficially simpler and is maintaining the port simpler than with my version? How do I update this if there is a new commit? With my version I bump the date and modify the commit hash like I do in quite a few of my other ports. I fear what you did will make my life more complicated.
