Hi, Jordi, I am glad you know what I said completely. Just one thing...the suggestion you made...exists. The Fedora way was introduced by early openSUSE go maintainers, I just renamed it to "-source" to better reflect what this sub-package really is. And I myself usually don't add that macro to my specfile. Because I don't like souce codes shipped to the end users. (traditionally, they recommends/requires the -source sub-package for the main package, so a user may have accidentally installed many source codes.) I must admit that I didn't realize the real purpose of -source sub-packages. I think I need further investigation on it to see if the binary (.a) of a package build with source codes of its dependencies contains "import" declarations. Because currently golang-packaging just unpack the result .a files and check "import" to determine runtime dependencies. And I don't what to argue about whether golang has real shared libraries. All I know is that I enabled building of *.sharedlibname stuff in our main go package. And I can build .so files that depends on them. So I think to add "Requires: golang(API)" to shared builds is a must. I know it may sounds tricky. But technically, I can check buildflags and place a plain text file in /tmp (the easiest way, just like the way I check importpath) to tell the golang.req/prov whether the build is shared or not. Then decide whether to add that Requirement. Just need some spare time. Nowadays I'm busy in fixing bugs that prevent packages built with gcc6. Marguerite -- To unsubscribe, e-mail: opensuse-go+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-go+owner@opensuse.org