Closed shantanugadgil closed 3 years ago
@shantanugadgil what is the use case? This would require a fairly small number of changes, and I would tend to agree that the go version isn't terribly relevant to the filename when we're only using one go version to do the build these days. On the other hand, I'm not sure this impacts package maintainers since they will probably be using the source tarball anyway? What pain does this cause you specifically?
No major pain, as my Makefile is already setup using the variables (as I mentioned).
The use case is just for simplicity, not super important, just have to keep updating two variables instead.of one. 🙂
so followup question: what are you packaging this for? I've been thinking that releasing an rpm or deb would be useful
so followup question: what are you packaging this for? I've been thinking that releasing an rpm or deb would be useful
Nothing. I just consume it. 🐒
I just happen to use a GNUmakefile to download various tools 🙊 , Fabio is one of them.
so followup question: what are you packaging this for? I've been thinking that releasing an rpm or deb would be useful
forgot to mention that day ... do you know of FPM? (https://github.com/jordansissel/fpm) to create the packages.
the project uses goreleaser, which does support creating packages in several popular formats. I might look into doing this for the next release.
Is there any particular advantage with having the Golang version as part of the file name? (I know once there were builds using two separate Golang versions)
as of now my automation has this ...
Just wondering if this can be simplified just to have the fabio version?