-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 06/12/2015 10:49 PM, William Hubbs wrote: > On Fri, Jun 12, 2015 at 10:02:41PM +0200, Kristian Fiskerstrand > wrote: >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 >>
... >> >> That said, I understand the structure. I don't like it, but I >> understand it, given that it is primarily only intended to be >> used within container/docker environments. >> >> Good luck trying to get it to play nice with a package manager >> though... > > The other issue is a lot of upstreams for go don't do releases at > all; you just grab everything live.A > > Does anyone know how third party go packages are being handled on > other distros? Well, if the workflow is building a container, then testing the exact version and if everything works, deploy it, then discard the container once it is outdated, i.e. no updates are performed on it (data is in its own separate container, so new versions are distributed by creating a new app container) this makes perfect sense, and scales across multiple app-containers working in parallel quite nicely. Since this is (as I understand it) the intention with Go in the first place, maybe the effort of making this cooperate with the rest of the system (PM), should also focus on this? rather than trying to make it fit with the regular structure we're already familiar with. - -- Kristian Fiskerstrand Public PGP key 0xE3EDFAE3 at hkp://pool.sks-keyservers.net fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3 -----BEGIN PGP SIGNATURE----- iQEcBAEBCgAGBQJVe0htAAoJECULev7WN52FhSoIAJh3QTR1IEHPXjxHWJZmG7iA UbeG41eniUM2bn55fNYBmy31idp4Mb3cr2qWo5eJlq51um1dQJdkFsdqZZSSjGm0 pHwngDprrGLmYE+uRd8ewjPfiZZXMsYmSIKNr4mmJgT+6pARnptt4rSrFiH4rGwE 3T2U+It+Yiyi+oKVH3YqyCReeWicwjXSLn3D4JX80rOAgo7YkiLb9Vxk6ilFWY8z pcQaGbj/nSXk5wKYCamKRTCFkqnSqbCc7L0pmXXqI7j+BJE/cfFRGxPjqWe4KkZr bLvRjdSqsN/k9M9GCxz8fKO0T0cyMuTloT311vZ1EiC7cpcyIpUs6D22bFgaehw= =gZ80 -----END PGP SIGNATURE-----
