On 1 Dec 2016, at 11:35 AM, Potter, Tim (HPE Linux Support) <timothy.potter@hpe.com> wrote: > > On 30 Nov 2016, at 7:20 AM, Dr. Tobias Quathamer <toddy@debian.org> wrote: >> >> Package: wnpp >> Severity: wishlist >> Owner: Dr. Tobias Quathamer <toddy@debian.org> >> >> * Package name : go-toml >> Version : 0.3.5-1 >> Upstream Author : Thomas Pelletier >> * URL : https://github.com/pelletier/go-toml >> * License : TODO >> Programming Lang: Go >> Description : Go library for the TOML language >> >> This library supports TOML (Tom's Obvious, Minimal Language) >> version v0.4.0. >> . >> TOML aims to be a minimal configuration file format that's >> easy to read due to obvious semantics. TOML is designed >> to map unambiguously to a hash table. TOML should be >> easy to parse into data structures in a wide variety >> of languages. > > Hi Tobias. I think the name for this package should be, according to the pkg-go > standards[1] golang-github-pelletier-go-toml. > > We already have a TOML parser (but more are OK since it's a dependency for > another package) with a source package named golang-toml, but it was created before > the particular version of the standard came into effect. After looking at the code a bit I think the package name was created automatically since dh-make-golang detected that binaries are created. Here's what I do for packages like this. * Run "dh-make-golang -type library github.com/foo/bar" to always create a library. Source package is called golang-github-foo-bar and it produces a golang-github-foo-bar-dev package. * If there is a binary being created add a binary package stanza to d/control and add the appropriate binaries. Take care not to package test binaries etc. * Think up a name for the binary package. This is tricky. (-: Regarding binary packaging naming my thoughts are If it's a major app then the binary and source package should be called the app name, e.g influxdb. For smaller utilities I usually name the binary package golang-foo, e.g for the TOML parser golang-toml but that name is already taken. And the full golang-github-pelletier-toml is pretty unwieldy. Not sure what to do here. Tim.
Attachment:
signature.asc
Description: Message signed with OpenPGP using GPGMail