> I'm sorry, but golang-github-dustinkirkland-golang-petname-dev is ridiculous.
Hey, you picked that import name. :) But yeah, I'm not going to be a stickler about it. I see you added a binary that followed the rule. Ideally the source would match too, so that if Debian packages this, we don't get duplicates in the archive. But we can cross that bridge when we come to it. > There are 3 different implementations of petname -- in shell, python, and golang -- each for easy consumption by users/developers in each of those languages. Yeah, I get that. I just don't see why it's important for a Go user or developer to care if the executable is shell or Go. (The library I totally understand, but the exec?) But not important. > Moving back to triaged as Dustin has now updated the packaging according to the golang packaging spec. I still have some beefs. Specifically, the code files are installed in the wrong location. They should be installed in /usr/share/gocode/src [1]. Using --buildsystem=golang will do the right thing for you (and then you have to adjust your .install files -- and maybe use the dh-exec rename trick to switch the binary name from petname to golang-petname). Again, I'm not sure why you skip the strip step. It looks like you could remove that stanza (and the now-no-op override_dh_auto_build stanza). [1] http://pkg-go.alioth.debian.org/packaging.html#_file_locations ** Changed in: golang-petname (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520687 Title: [MIR] golang-petname-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-petname/+bug/1520687/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
