Not entirely sure I follow, but: 1. The value of debian/rules’s DH_GOPKG must always match the value in debian/control’s Xs-Go-Import-Path.
2. Using DH_GOPKG in debian/rules at all is only necessary when you need to reference it from build rule overrides, e.g. https://sources.debian.org/src/golang-go-dbus/1~bzr20150122-3/debian/rules/?hl=14#L14. This is rarely necessary. Does that help? On Fri, Dec 21, 2018 at 4:24 PM Tong Sun <[email protected]> wrote: > On Wed, Dec 19, 2018 at 1:52 PM Michael Stapelberg wrote: > > >> > On Sun, Dec 16, 2018 at 5:24 AM Tong Sun wrote: > >> >> > >> >> Does Binary-only package still need to set the DH_GOPKG variable? > >> >> > >> >> >From https://go-team.pages.debian.net/packaging.html, it says: > >> >> > >> >> - - - - - - - - > >> >> dh-golang comes with an example debian/rules file: > >> >> > https://salsa.debian.org/go-team/packages/dh-golang/blob/master/example/rules > >> >> > >> >> You will need to change the value of DH_GOPKG to correspond to your > >> >> program’s upstream package name. > >> >> - - - - - - - - > >> >> > >> >> Is such "changing the value of DH_GOPKG" step still necessary? > > > Done: > https://salsa.debian.org/go-team/packages/dh-golang/commit/c3e82714f47ca715aae2ceae5f32297180a09285 > > Thanks a lot Michael! > > I hope somebody else can step forward to change the wording in the > above doc as well, emphasizing that "changing the value of DH_GOPKG" > is necessary *only* under some very specific cases (which I am not > clear myself yet). > > Thx! > > -- Best regards, Michael
