Thanks for the package update and included fix. The consumer package dwarf2json you mention will not need to depend on this package. There are two distinct eras of Go packaging:

1) setting up dependencies under GOPATH , and

2) when using go modules, use "go mod vendor" to pull in pinned dependencies to vendor/.

The former style the one described in the wiki [], and the current packaging style is automated by obs-service-go_modules [*]. I am inserting a new section to the wiki page to introduce obs-service-go_modules for those packaging new applications while preserving the information about the pre-modules method.

I will create an SR to dwarf2json to use obs-service-go_modules shortly, thanks for packaging it.

[] https://en.opensuse.org/openSUSE:Packaging_Go [*] https://github.com/openSUSE/obs-service-go_modules/

Hans-Peter Jansen (frispete) - over 3 years ago

author

Thanks, Jeff, for the detailed notes. For an uninvolved person, the whole state of Go packaging is pretty confusing, to put it mildly.

I'm awaiting your adjustments to dwarf2json and the wiki in order to learn more lessons from this chapter.

There's another go package, that does strange things in this regard: syncthing[1]. It really deserves some loving touches.

[1] https://build.opensuse.org/package/show/network/syncthing

@andtecheu, @cyphar, @flavio_castelli, @jfkw, @jordimassaguerpla: review reminder