[opensuse-go] Golang packaging in openSUSE
Hi I’m interested in packaging golang libraries for openSUSE. I was following the wiki [1] and submitted some of the packages to devel:languages:go [2] and ultimately requested a sync to Factory [3]. Along the way I found discrepancies between how packages actually look like and how they are described on the wiki. I would like to understand how to correctly provide library packages and update the wiki page if necessary. My question is this: the review feedback was Get rid of source subpackage, no one use it Is this accurate? I thought that the source package is what is actually used to build executables because of the golang ABI stability issues. Best regards ZK [1] https://en.opensuse.org/openSUSE:Packaging_Go [2] https://build.opensuse.org/request/show/407931 [3] https://build.opensuse.org/request/show/408354-- To unsubscribe, e-mail: opensuse-go+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-go+owner@opensuse.org
On Fri, Jul 22, 2016 at 2:59 PM, Zygmunt Krynicki
Hi
I’m interested in packaging golang libraries for openSUSE. I was following the wiki [1] and submitted some of the packages to devel:languages:go [2] and ultimately requested a sync to Factory [3]. Along the way I found discrepancies between how packages actually look like and how they are described on the wiki. I would like to understand how to correctly provide library packages and update the wiki page if necessary.
My question is this: the review feedback was Get rid of source subpackage, no one use it
Hi, Zygmunt, Yes, the wiki page is outdated. It was drafted by me about two years ago. Later then I began golang-packaging so most of what the wiki said should be updated. There's a meeting scheduled for the future of golang packaging in openSUSE recent days. So I can't tell more what the precedure will be right now. Please just wait for a few days (10 to 20 days) until we have a solution. PS: "Is this accurate? I thought that the source package is what is actually used to build executables because of the golang ABI stability issues." In my opinion: Yes it's accurate. the .a file acts the same as the .go source codes. except for one thing: .a is the build result under a specific version of golang. No one knows if the .go is buildable unless we have got .a. So if an ABI change breaks the build, the source package will just hide it. And executables is not built from .go directly but from .a. Marguerite -- To unsubscribe, e-mail: opensuse-go+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-go+owner@opensuse.org
participants (2)
-
Marguerite Su
-
Zygmunt Krynicki