one of my pet hates as a #golang programmer is go projects that violate the entire point of the Go tooling by making some gay ass complicated shit about how to install some thing that is 100% go
henlo
go install .
gfy moron makefile user
Discussion
my specific complaint right now is about `golangci-lint`
which ackchually you can install just by cloning the repo and `go install ./cmd/golangci-lint/.` like a FUCKING NORMAL GO PROGRAM
why this does not appear at the top of the "how to install" documentation is beyond me but fuck these dickheads, they need to be slapped upside their heads lol
If day = "Saturday" then
Go and play!
Else
Does this option exist if you're not supposed to be doing it
End if
I'm just kidding 😂 I like people who disrespect the weekends/weekday thing.
well, basically, i'm forking a thing that uses makefiles and does this gay homo shit aand i was just remarking upon how gay and homo it is
and i was right, i was able to build it with a normal fucking go install command
it is just the first step, i'm gonna get into it more tomorrow, yes tonight is holiday and i'm kinda tired because i woke up at 3am this morning so probably just gonna play some tomb raider game for the rest of my evening and sleep not long after the light is gone
this is the thing i need to fix, because it has gay and homo rust code bindings to it, and there is now a pure and light version that is in go so i think it's possible i can expurgate the sinful rust from its bowels and put in its place the saintly go verison
i'm not going to get into the fact that it's a shitcoin, oh shit, i just did.
but if it's a shitcoin, at least let it be only go and not hipsterlang vomit
The saintly Go version :-D hehehe.
Shitcoin? If it's what the people want!
Some people like stain glass windows.
doas make install
lol, no, gfy
go install .
or
go install ./cmd/programname/.
i should not have to get root to fucking install an application ffs
export GOBIN=$HOME/.local/bin
export PATH=$GOBIN:$PATH
or GTFO
in my opinion, an entire operating system could be built on this one tool, if only the hipsters and the greybeards would see the sense of the middle way
I admit was really impressed when I discovered that I was compiling and installing binaries in userspace by default.
With makefiles you can just "make install", it could be problematic just with libraries that need to be eventually symlinked in root. Binaries can be installed to .local/bin in userspace and most of the time they just work, you need to see if the path is exposed as env variable and they will act as expected and even pop-up in the various DE- menus...
