On Sun, Dec 24, 2023 at 01:41:39PM +0530, Ananthu C V wrote: > It looks that this has been a clear oversight from my side. *I do find this a very useful library* > but as you mentioned, since go team convention does not include packaging libaries that are not > needed by any binaries, there is probably no real value in getting this in. It is not a go-team convention as such. In principle library packages can be packaged as well. However there is no utility in doing so. At the end of the day, a user only wants the necessary tools. The situation is quite different from python or javascript (where you work). In those teams, once you install python lib or a js lib, you can use it for your development w/o any extra hurdles. All imports/functionalities would work just fine. However, in go packages, you need to change the GOPATH/GOROOT to actually import and use those packages. This makes close to no sense for anyone to do, and simply using a go get is the most simple way. Adding in lib packages that effectively won't be used also calls for extra maintenance burden on the team so at least I find it sensible to add lib packages only when there's a use for them. > As such, please prune the corresponding repositories for the following: > - golang-github-apenella-go-ansible > - golang-github-apenella-go-common-utils > - golang-github-sosedoff-ansible-vault-go Pruned! > I feel sincerely sorry that an oversight from my side has ended up taking some of your busy schedule > and I apologize for making you spend your time needlessly. I'll try my best to make sure such mishapas > does not occur in the future, since it is not beneficial to anyone. And regardless of the outcome of > this, thanks a lot for taking a look at the RFS. Don't worry about it, thanks for working on these regardless! Best, Nilesh
Attachment:
signature.asc
Description: PGP signature