<div dir="ltr"><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">> I'm not asking for extensive and comprehensive explanations. </blockquote><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">> I'm only asking for some simple instruction on the major steps/tools</blockquote><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">> involved.

</i>

</blockquote><div> </div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">

dh-make-golang gets you started by creating a gbp-style repo, containing the basic Debian packaging files.

For very simple packages it's already enough and works out of the box, although you still need to edit a few things here and there.

For more complicated packages, consider the packaging files generated as a starting point. Then you will have to use your debian packaging skills, and look at other similar packages, to work your way to a working package.

Notice that you must be familiar with git buildpackage (gbp), because that's where dh-make-golang takes you, with 3 branches: 'master', 'upstream' and 'pristine-tar'. If you have never worked with gbp before you will have a hard time.

As for `dh-golang`, it is used to build golang packages indeed. If you<br>look at the `debian/rules` file generated by dh-make-golang, you will<br>see something like `dh $@ --buildsystem=golang --with=golang`. This is<br>what triggers the use of dh-golang.</blockquote><div><br></div><br><div>Thanks for the detailed explanation Arnaud. This is exactly kind of things I was looking for. </div><div><br></div><div>I know we new maintainers need to connect the dots ourselves, but the problem is I don't even know what dots to connect, having already read all the go packaging materials I can find, despite the fact that I know how to maintain normal Debian packages, and have already maintained several. E.g., this is the first time I realized that gbp is involved (I admit that I only paid attention to the comments/instructions, not lines after lines of the code. Well, to be accurate, I noticed the `gbp` three character when I first read <a href="https://pkg-go.alioth.debian.org/packaging.html">https://pkg-go.alioth.debian.org/packaging.html</a>, but I had no clue what it is and had made a todo item to lookup for what `gbp` stands for). </div><div><br></div><div>Maybe it is a more a personal taste, but I'd like to read before leap. </div><div><br></div><div><i>Just as a comparison</i>, some people would swirl into action on only see this <b id="gmail-docs-internal-guid-f9e6a55d-c118-2cc0-3431-41e8de1b5ddf" style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;font-weight:normal"><span id="gmail-docs-internal-guid-f9e6a55d-c118-2cc0-3431-41e8de1b5ddf"><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;display:inline!important"><span style="color:rgb(17,85,204);text-decoration-line:underline;font-size:11pt;font-family:Arial;background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap"><a href="https://docs.microsoft.com/en-us/azure/cloud-shell/quickstart" style="text-decoration-line:none">quickstart</a></span> on </p></span><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;background-color:rgb(255,255,255);display:inline"><b id="gmail-docs-internal-guid-f9e6a55d-c118-2cc0-3431-41e8de1b5ddf" style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;background-color:rgb(255,255,255);font-weight:normal"><b id="gmail-docs-internal-guid-f9e6a55d-c118-2cc0-3431-41e8de1b5ddf" style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;font-weight:normal"><span style="color:rgb(0,120,215);text-decoration:underline;font-size:12pt;font-family:Arial;background-color:rgb(255,255,255);font-weight:400;font-style:normal;font-variant:normal;vertical-align:baseline;white-space:pre-wrap"><a href="https://docs.microsoft.com/en-us/azure/cloud-shell/quickstart" style="color:rgb(17,85,204);text-decoration:none">Cloud Shell</a></span></b></b></p></b>:</div><div><br></div><div><b style="font-weight:normal" id="gmail-docs-internal-guid-f9e6a55d-c118-2cc0-3431-41e8de1b5ddf"><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;background-color:rgb(255,255,255)"><a href="https://docs.microsoft.com/en-us/azure/cloud-shell/quickstart" style="text-decoration:none"><span style="font-size:12pt;font-family:Arial;color:rgb(0,120,215);background-color:rgb(255,255,255);font-weight:400;font-style:normal;font-variant:normal;text-decoration:underline;vertical-align:baseline;white-space:pre-wrap">Cloud Shell Quickstart</span></a></p><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt"><a href="https://docs.microsoft.com/en-us/azure/cloud-shell/quickstart" style="text-decoration:none"><span style="font-size:11pt;font-family:Arial;color:rgb(17,85,204);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:underline;vertical-align:baseline;white-space:pre-wrap">https://docs.microsoft.com/en-us/azure/cloud-shell/quickstart</span></a></p></b><br class="gmail-Apple-interchange-newline">But I'd like to read more before following suit to create my own Azure VM, because there are so much info missing for the <b id="gmail-docs-internal-guid-f9e6a55d-c118-2cc0-3431-41e8de1b5ddf" style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;background-color:rgb(255,255,255);font-weight:normal"><span id="gmail-docs-internal-guid-f9e6a55d-c118-2cc0-3431-41e8de1b5ddf"><p dir="ltr" style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;display:inline"><span style="color:rgb(17,85,204);text-decoration-line:underline;font-size:11pt;font-family:Arial;background-color:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap"><a href="https://docs.microsoft.com/en-us/azure/cloud-shell/quickstart" style="color:rgb(17,85,204);text-decoration-line:none">quickstart</a></span></p></span></b>. </div><div><br></div><div>I'd like to use the same approach for go packaging as well, if possible, but I have found so many missing steps when it comes to go packaging. </div><div>E.g. (apart from what `gbp` stands for) what steps needs in turning from <a href="https://github.com/containerd/continuity">https://github.com/containerd/continuity</a></div><div>to <a href="https://salsa.debian.org/go-team/packages/continuity">https://salsa.debian.org/go-team/packages/continuity</a>?</div><div><br></div><div>maybe it is really trivial, but then it doesn't need much explanation either. Otherwise, it becomes a missing step for new maintainers. </div><div><br></div><div>Moreover, speaking of gbp, is it still the correct tool to use when I'm also the upstream author? E.g., will the 3 branches: 'master',</div><div>'upstream' and 'pristine-tar', still necessary? Or we'd better keep them separated just like what <span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><a href="https://salsa.debian.org/go-team/packages/continuity">https://salsa.debian.org/go-team/packages/continuity</a> is doing? But wouldn't it double the amount of work? </span></div><div><br></div><div>Overall, I know it is not hard for all your experienced go maintainers, but some might have forgot how hard it was for the new comers to pick up. Well, I must stop complaining, and give up my "look before leap" motto, and start cracking... </div><div><br></div></div>