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
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
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-
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
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
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