Re: gopasspw packaging (#901133)

2020-01-19 Thread Balasankar "Balu" C
Hi, On 19/1/20 9:22 PM, Thorsten Alteholz wrote: > Hi, > > On Fri, 17 Jan 2020, Balasankar "Balu" C wrote: >> 2. github.com/hashicorp/vault >> >> vault is a bit big[0] and a bit tricky. gopasspw does not require the >> entire vault codebase, but parts of it. >> Specifically things from api[1] and

Re: gopasspw packaging (#901133)

2020-01-19 Thread Thorsten Alteholz
Hi, On Fri, 17 Jan 2020, Balasankar "Balu" C wrote: 2. github.com/hashicorp/vault vault is a bit big[0] and a bit tricky. gopasspw does not require the entire vault codebase, but parts of it. Specifically things from api[1] and sdk[2] directories. isn't your vault related to [1]? Probably tha

Re: gopasspw packaging (#901133)

2020-01-17 Thread Shengjing Zhu
It might be interesting to try, since they are two Go modules, and in one repo. -- Shengjing Zhu

Re: gopasspw packaging (#901133)

2020-01-17 Thread Balasankar "Balu" C
Hi, On 17/1/20 7:23 PM, Balasankar "Balu" C wrote: > Yes. I am trying to figure out if dh's Golang build system can do it or not. I found that there are packages like syncthing, influxdb, toxyproxy, etc. which do multiple binary packages. Let me check them out. Regards Balu signature.asc Des

Re: gopasspw packaging (#901133)

2020-01-17 Thread Balasankar "Balu" C
Hi, On 17/1/20 5:38 PM, Pirate Praveen wrote: > > On വെ, Jan 17, 2020 at 17:31, Balasankar Balu C > wrote: >> I think the plan is to have a `vault` source package, that currently >> only builds/installs `golang-github-hashicorp-vault-api` >> and `golang-github-hashicorp-vault-sdk` binary packages

Re: gopasspw packaging (#901133)

2020-01-17 Thread Pirate Praveen
On വെ, Jan 17, 2020 at 17:31, Balasankar Balu C wrote: Hi, On 17/1/20 3:14 PM, Clément Hermann wrote: In any case, it would be interesting to answer this question anyway: how do we make sure we don't have duplicate code in packages when we do this ? I think the plan is to have a `vau

Re: gopasspw packaging (#901133)

2020-01-17 Thread Balasankar "Balu" C
Hi, On 17/1/20 3:14 PM, Clément Hermann wrote: > In any case, it would be interesting to answer this question anyway: > how do we make sure we don't have duplicate code in packages when we > do this ? I think the plan is to have a `vault` source package, that currently only builds/installs `gola

Re: gopasspw packaging (#901133)

2020-01-17 Thread Clément Hermann
Hi, On 17/01/2020 10:13, Balasankar "Balu" C wrote: > Hi, > > On 17/1/20 2:38 PM, Pirate Praveen wrote: >> We discussed about packaging only part of bigger repos recently and >> agreed on packaging parts, just package vault-api and vault-sdk. > > That also works (Though I am not sure how that w

Re: gopasspw packaging (#901133)

2020-01-17 Thread Pirate Praveen
On വെ, Jan 17, 2020 at 14:43, Balasankar Balu C wrote: Hi, On 17/1/20 2:38 PM, Pirate Praveen wrote: We discussed about packaging only part of bigger repos recently and agreed on packaging parts, just package vault-api and vault-sdk. That also works (Though I am not sure how that will

Re: gopasspw packaging (#901133)

2020-01-17 Thread Balasankar "Balu" C
Hi, On 17/1/20 2:38 PM, Pirate Praveen wrote: > We discussed about packaging only part of bigger repos recently and > agreed on packaging parts, just package vault-api and vault-sdk. That also works (Though I am not sure how that will turn out if/when we actually want to package Vault). Do we ha

Re: gopasspw packaging (#901133)

2020-01-17 Thread Pirate Praveen
On 2020, ജനുവരി 17 1:07:54 PM IST, "Balasankar "Balu" C" wrote: >Hi, > >On 30/3/19 8:01 PM, Balasankar C wrote: > >> Hi all, I am interested in packaging gopasspw[0], and have marked the >corresponding bug(#901133) to an ITP. >> I have written a few Go programs as hobby projects, but am new to

Re: gopasspw packaging (#901133)

2020-01-16 Thread Balasankar "Balu" C
Hi, On 30/3/19 8:01 PM, Balasankar C wrote: > Hi all, I am interested in packaging gopasspw[0], and have marked the corresponding bug(#901133) to an ITP. > I have written a few Go programs as hobby projects, but am new to packaging (I usually package Ruby libraries). > So, any help is much apprec

Re: gopasspw packaging (#901133)

2019-04-21 Thread Jongmin Kim
On Sun, Apr 21, 2019 at 11:36:26AM +0530, Balasankar C wrote: > Please go ahead. We haven't started packaging it. Also, we are > maintaining our progress in the wiki[0], so everyone can get a quicker > glance. > > [0] https://wiki.debian.org/Teams/DebianGoTeam/GopasspwPackaging > > > > > This pa

Re: gopasspw packaging (#901133)

2019-04-20 Thread Balasankar C
Hi Jongmin, On 4/21/19 5:29 AM, Jongmin Kim wrote: > Hi Balasankar and all, > > On Sat, Mar 30, 2019 at 08:01:59PM +0530, Balasankar C wrote: >> Hi all, >> >> I am interested in packaging gopasspw[0], and have marked the >> corresponding bug(#901133) to an ITP. I have written a few Go programs >>

Re: gopasspw packaging (#901133)

2019-04-20 Thread Jongmin Kim
Hi Balasankar and all, On Sat, Mar 30, 2019 at 08:01:59PM +0530, Balasankar C wrote: > Hi all, > > I am interested in packaging gopasspw[0], and have marked the > corresponding bug(#901133) to an ITP. I have written a few Go programs > as hobby projects, but am new to packaging (I usually package

gopasspw packaging (#901133)

2019-03-30 Thread Balasankar C
Hi all, I am interested in packaging gopasspw[0], and have marked the corresponding bug(#901133) to an ITP. I have written a few Go programs as hobby projects, but am new to packaging (I usually package Ruby libraries). So, any help is much appreciated. dh-make-golang reported the following packa