Hello, Is there anything special to consider for packaging go libraries?
When brentp implements a buffered reader for go, something rather essential I tent to think, is the proper package name then xopen brentp-xopen golang-xopen or golang-brentp-xopen? Should we somehow coordinate who addresses the packaging of what? Some GO aficionado here who would like to adopt them all? Best, Steffen On 28.05.19 10:22, Steffen Möller wrote:
GitLab # *debian/changelog* <https://salsa.debian.org/med-team/vcfanno/commit/a8ad5a8157284425a698ec9168dde78939b2b733#9c96da0e9f91d7d8937b69b524702c106258f0d1> ------------------------------------------------------------------------ 1 1 vcfanno (0.3.1-1) UNRELEASED; urgency=medium 2 2 3 3 * Initial release (Closes: #<bug>) 4 + 5 +[Steffen Moeller] 6 + 7 +* Far from being releaseable, requiring 8 +"github.com/BurntSushi/toml" 9 +"github.com/biogo/hts/bgzf" 10 +"github.com/brentp/irelate" 11 +"github.com/brentp/irelate/interfaces" 12 +"github.com/brentp/irelate/parsers" 13 +"github.com/brentp/vcfanno/api" 14 +"github.com/brentp/vcfanno/shared" 15 +"github.com/brentp/vcfgo" 16 +"github.com/brentp/xopen" 4 17 5 18 -- Andreas Tille <[email protected]> Wed, 17 Apr 2019 10:48:54 +0200 19 + \ No newline at end of file
_______________________________________________ debian-med-commit mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-commit
